| 02:41 | cbxbiker61 | i just received my hummingboard i2ex, it's a sweet piece of kit |
| 02:42 | cbxbiker61 | now i just need to figure out why it's resetting about the time I get xbmc loaded (i used a card working in a cubox-i4) |
| 12:04 | joost_dtn | okay, which linux image should i use to get decent, proper working bluetooth connectivity for my cubox-i2ultra |
| 12:06 | joost_dtn | the closest thing to get it working was on geexbox, which was my original goal to begin with to get it working with that |
| 12:07 | joost_dtn | figured that i might just as well try on a regular distribution |
| 12:08 | joost_dtn | the current jessie image doesn't even have a proper kernel that has bluetooth enabled it seems |
| 12:10 | joost_dtn | been searching on the geexbox forums, the cubox forums and even plain debian forums and tried every suggestion, but it all fails |
| 12:10 | joost_dtn | on the geexbox image i do get to see the bluez controller, am able to power it up, but scans do not show up anything, not using hcitool or bluetoothctl |
| 13:03 | jnettlet | root |
| 13:13 | cbxbiker61 | i've just been doing a bit of experimentation with ffmpeg/x265 |
| 13:14 | cbxbiker61 | found out that my couple of year old quad core notebook is fast enough to decode, which is a good thing |
| 13:15 | cbxbiker61 | a quick look at cpu utilization on my amd 5350 showed the cores running at about 60%, so i don't think the quad cubox-i is going to be quite enough |
| 13:16 | cbxbiker61 | i also think most of the assembler optimations in x265 are for x86 |
| 13:19 | cbxbiker61 | wasn't too long ago the x265 guys were saying "desktop" level machine, nice to see the progress to running fine on a notebook |
| 13:20 | bencoh | x265 running fine ? |
| 13:20 | bencoh | well I guess you're not talking about live encoding :) |
| 13:20 | cbxbiker61 | it looks good to me |
| 13:21 | bencoh | (decoding in ffmpeg isnt done by x265 btw) |
| 13:22 | cbxbiker61 | i've got dueling ffmpeg's running right now, so all i can say is that even though half of the cpu is soaked up by another process, i'm doing about 20fps encoding on an 4.7GHz 8 core |
| 13:23 | cbxbiker61 | 720p @ crf 24 |
| 13:23 | bencoh | yeah, not ready for live ;) |
| 13:23 | cbxbiker61 | tell ya what... |
| 13:24 | cbxbiker61 | they've been working on opencl support, but haven't released the code yet |
| 13:25 | cbxbiker61 | at least the h265 spec was written with parallel processing in mind |
| 13:27 | cbxbiker61 | if opencl with a good card could boost that 3-4 times, we'd be in relatively good shape |
| 13:30 | joost_dtn | just tried archlinux using the wiki instructions, on linux 3.10 kernel, with the firmware installed: no dice. |
| 13:30 | joost_dtn | starting to suspect bluetooth hardware failure |
| 14:56 | joost_dtn | okay. may it be forever noted that for bluetooth to work on a Cubox i2ultra, you need to make sure that brcm_patchram_plus needs to be invoked WITHOUT --enable_lpm |
| 15:00 | joost_dtn | One parameter '--enable_lpm' would send a 'hci_sleep_cmd' to Bluetooth chip, which means that Bluetooth chip may 'sleep' at some time after that command has been sent. So, I tried to remove it from the command, and bluetooth works well afterwards. |
| 15:19 | balrog | joost_dtn: is the chip sleeping and not waking up? |
| 15:20 | joost_dtn | apparently |
| 15:20 | joost_dtn | tried all major distro's and images, all had the same trouble |
| 15:21 | joost_dtn | found out in some unrelated github project about that --enable_lpm switch |
| 15:21 | joost_dtn | removed it from geexbox' start-brcm-patcram-plus script and it worked instantly |
| 20:08 | msalerno | Archlinux - Has anyone gotten bluetooth working? |