01:28 | alpha_one_x86 | Hello, cubox-i have disable at idle if don't use the float/neon part? |
04:31 | cbxbiker61 | i'm finally in a good place WRT cubox-i, i have my distro running on the hardware and i'm in the process of bringing all of the packages up to speed |
06:21 | cbxbiker61 | the hummingboard is getting coverage at http://linuxgizmos.com/ |
06:28 | jnettlet | cbxbiker61, yeah wondering where that came from. Last I knew they weren't really pushing the quad-core variant. It of course works, but then there needs to be some sort of heat sink added. |
06:29 | cbxbiker61 | if you read further in the article they mention single/dual, i think they may have just mislabeled the article |
06:30 | jnettlet | I saw something like that on another MX6 board yesterday. http://www.cnx-software.com/2014/04/22/habey-hio-project-arm-board-and-hio-wallpad-poe-automation-panel-crowdfunding/ |
06:31 | jnettlet | it mentions a quad-core up at the top of the article. I am looking at that design and thinking...not gonna work |
08:33 | davorin | android in the wall? *iik |
08:35 | jnettlet | it is mx6 so you can run linux on it |
08:35 | davorin | yeah i know... |
08:35 | davorin | in my opinion generates too much heat in a small wall outlet |
08:36 | jnettlet | the dual-lite shouldn't be too bad |
08:37 | davorin | but still...a little overkill (o; |
08:37 | jnettlet | depends what you want to do with it. |
08:38 | jnettlet | but for anything with a touchscreen I really think you want a dual-core processor, even clocked down just to make it as interactive as possible |
08:38 | davorin | my design is different, as it would replace either a switch or measure current consumption... |
08:39 | davorin | and depending on the country...it might be difficult to add extra wires to power it... |
08:39 | davorin | for example in germany |
08:39 | jnettlet | that is why it supports POE |
08:39 | davorin | yes...quite common in homes (o; |
08:40 | jnettlet | but it is a single cable that can easily be run in external molding. |
08:40 | jnettle | 08:40 * jnettlet hates the horrible Danish walls. Give me sheetrock any day. So much easier to add updated wiring. |
08:41 | davorin | in .ch it would be easier....as most eletric installation use plastic tubes inside the wall... |
08:41 | davorin | where the cables are pulled through.... |
08:41 | davorin | so you could easily add new cables... |
08:41 | jnettlet | conduits, sure more modern. |
08:42 | davorin | i haven't just figured out a way how to power a device in series of a lamp for example...and be used as a switch |
08:43 | davorin | and i would add some more sensors in each socket... |
08:43 | davorin | temp and humidity at least... |
08:44 | davorin | motion as well... |
08:44 | jnettlet | could be done with a raspberry pi expansion board on the hummingboard |
08:45 | davorin | temp/humidity is just a simple sensor...can be connected directly via gpio, like the dht11 or the am2302 |
08:45 | davorin | but haven't found small enough pir sensors... |
08:49 | davorin | those banana pi guys are bugging me..... |
08:49 | davorin | writing every day if i want to sell it (o; |
15:04 | wbx | what is the status of usb in 3.14.1? |
17:07 | _dab_ | rabeeh: looking at rmks long list of fec patches. Is it time to restest my FEC problem on 3.15? |
17:15 | jnettlet | _dab_, yes please |
17:56 | msalerno | Has anyone got linux and bluetooth working on linux? I've read through the forums, but none of the proposed solutions work |
17:57 | jnettlet | msalerno, it should be working under geexbox. |
17:58 | msalerno | I'll make a new image and see how it works. I'm trying to get it working on Arch |
18:02 | rabeeh | msalerno: please update the wiki if you have more info |
18:47 | wbx | hmm. is the framebuffer supported in 3.14.1? |
18:48 | mk01 | msalerno: BT works. |
18:49 | mk01 | msalerno: on Arch is kind of problem though. |
18:50 | msalerno | @mk01 been working on it for the last few days on and off. Been making me crazy. |
18:50 | jnettlet | wbx, via the staging KMS/DRI driver yes. |
18:51 | wbx | jnettlet: wiki says video=mxcfb0:dev=hdmi, but isn't the name of the driver mxsfb? |
18:53 | jnettlet | wbx, that is for the 3.10.30 kernel, not the upstream 3.14.xxx and > |
18:53 | wbx | jnettlet: ah. so all I want is in staging/imx-drm/ |
18:54 | mk01 | msalerno: I sent everything (fw, kernel config related to BT, ...) to Pepedog. the setup works fine on Debian (XBian). there is no reason not to work with Arch |
18:54 | jnettlet | wbx, you got it |
18:55 | jnettlet | wbx, you won't have accelerated graphics with the upstream kernel. |
18:55 | jnettlet | just an fyi |
18:56 | wbx | jnettlet: oh. so if I would like to try xbmc I am fixed to 3.10.x usage? btw, when do you update to 3.10.37? |
18:57 | jnettlet | wbx, yes. I will be starting the rebase onto 3.10.37 this weekend. When it is out depends on how much has changed and how much time I end up having. I am hoping to finish it this weekend. |
18:57 | wbx | jnettlet: cool. |
18:57 | msalerno | mk01: He has posted many of those files in the forums, but it doesn't seem to work. I can only guess that it's a kernel config issue. I've rebuilt my kernel based on recommendations i found in the forums. Still doesn't work |
18:58 | jnettlet | wbx, after that I will work on breaking out galcore and a few other drivers to a separate repo that can be compiled against upstream |
18:58 | msalerno | mk01: is 3.10 used on XBian? |
18:58 | rabeeh | msalerno: you first need to figure out if you using 4329 or 4330 |
18:59 | mk01 | rabeeh: in the fw pack there is 29 and 30 as well. |
18:59 | wbx | jnettlet: what is galcore? |
19:00 | rabeeh | mk01: but for the bt, the patchram command is different |
19:00 | msalerno | rabeeh: how do I determine that? this is my first arm system. I'm used to lspci |
19:00 | rabeeh | wbx: galcore is the kernel GPU driver |
19:00 | rabeeh | msalerno: it's under /sys/class/mmc/mmc0 ... |
19:01 | rabeeh | wifi/bt is connected via sdio interface (not pci) |
19:01 | wbx | and the GPU driver runs independent to the imx-drm fb driver? or does it require the ixm-drm? |
19:01 | msalerno | Right, no PCI which is why I wasn't sure where to look |
19:01 | rabeeh | i don't have a system booted around to ssh to it; but dig inside that directory and you should see a file called device |
19:01 | rabeeh | just 'cat' it and it will be 4329 / 4330 |
19:01 | rabeeh | mal-: welcome |
19:02 | mk01 | msalerno: yes. try recompile with XBian's .config. It's in the Arch discussion (cut of it), but here is the link https://github.com/xbianonpi/xbian-patches/blob/master/kernel.i.MX6/config |
19:02 | mk01 | rabeeh: ah ok |
19:03 | mk01 | msalerno: /sys/class/mmc_host/mmc0/mmc0:0001/mmc0:0001:2/device |
19:04 | mk01 | rabeeh: what's the command for 4330 ? |
19:04 | msalerno | 0x4330 |
19:04 | rabeeh | mk01: what happened to your new CBi / HB? |
19:04 | rabeeh | malte told me they were delivered to you? |
19:05 | mk01 | rabeeh: no, they were returned from Customs. |
19:05 | mk01 | rabeeh: problem was that once it get's into the system - it can't be changed |
19:06 | mal- | rabeeh: hello |
19:06 | mal- | :) |
19:06 | msalerno | [root@mycubox-i mmc_host]# find /sys/class/mmc_host/*/*/* -maxdepth 1 -name device -exec cat {} \; |
19:06 | msalerno | 0x4330 |
19:06 | rabeeh | mk01: so they are return to SolidRun or what? |
19:07 | mk01 | rabeeh: I suppose, yes. |
19:07 | msalerno | Following mk01's question: rabeeh, what's the command for the 4330? |
19:07 | rabeeh | hmm... i'll check with Riki then |
19:07 | rabeeh | this is what i use for android on 4330 |
19:08 | rabeeh | brcm_patchram_plus -d --patchram /tmp/bcm4330.hcd --baudrate 3000000 --enable_hci --use_baudrate_for_download /dev/ttymxc3 --no2bytes --enable_lpm --tosleep=50000 |
19:08 | rabeeh | oh; sorry |
19:08 | rabeeh | that line was actually developed under buildroot |
19:08 | rabeeh | as i recall the additions are '--enable_lpm' |
19:08 | rabeeh | notice that you need the rfkill part also in the kernel |
19:11 | msalerno | rabeeh: is CONFIG_MACH_IMX_BLUETOOTH_RFKILL part of that requirement ? |
19:12 | rabeeh | which kernel are you running? |
19:12 | msalerno | 3.10.30-15-ARCH |
19:13 | msalerno | which does not have that option |
19:13 | rabeeh | true |
19:13 | rabeeh | LK 3.0.35 had that and it's required |
19:13 | rabeeh | i don't see that option on LK 3.10.30 |
19:14 | msalerno | hcitool dev is now returning hci0 |
19:15 | rabeeh | congrats |
19:15 | rabeeh | now inq it :) |
19:16 | rabeeh | send inquery and see what happens |
19:19 | msalerno | I sent: hciconfig hci0 up |
19:20 | msalerno | however, "hcitool scan" eventually returns "Inquiry failed: Connection timed out" |
19:21 | msalerno | same with hcitool inq |
19:23 | rabeeh | so it's not working then |
19:25 | mk01 | msalerno: what "Bus:" is the device on in "hciconfig" output ? |
19:25 | mk01 | UART or SDIO ? |
19:27 | msalerno | Bus: UART |
19:28 | mk01 | ok |
19:28 | mk01 | and is listed as DOWN ? |
19:28 | msalerno | UP RUNNING |
19:29 | mk01 | then try "hcitool scan" |
19:29 | mk01 | root@cubox:/etc/init# hcitool scan |
19:29 | mk01 | Scanning ... |
19:29 | mk01 | 40:5F:BE:72:5D:5D namarse |
19:29 | mk01 | E4:E0:C5:DE:88:C0 DTVBluetooth |
19:29 | msalerno | # hcitool scan |
19:29 | msalerno | Scanning ... |
19:29 | msalerno | Inquiry failed: Connection timed out |
19:29 | mk01 | and "dmesg | tail" ? |
19:30 | msalerno | [ 129.775598] Bluetooth: hci0 command 0x0401 tx timeout |
19:30 | mk01 | hm |
19:32 | msalerno | I think i'm loading the wrong firmware |
19:32 | msalerno | rechecking |
19:36 | wbx | hmmm. don't get the framebuffer via hdmi connected to a LG display working. anything wrong in my dmesg? http://www.openadk.org/cubox/dmesg.txt |
19:36 | msalerno | Grabbed firmware from Geexbox |
19:36 | msalerno | 8e32f9168aaa540467589c153129c57a /lib/firmware/brcm/bcm4330.hcd |
19:36 | msalerno | same result |
19:48 | mal- | mk01 |
20:43 | phil_m | Hi rabeeh. Phil from Manjaro here. My developer box is now at customs in Rosenheim. I'll try to call the office so they might ship it to me or to another customs office which is nearer to my office. Maybe an email from your end might help me. Malte already sent me a letter regarding this. |
20:43 | mal- | hi |
20:44 | phil_m | hi mal- |
20:44 | mal- | pm |
20:48 | jnettlet | phil_m, I was just looking at manjaro yesterday. I have been telling myself I need to try Arch but don't want all the hassle. Let me know if there is anything I can do to help you out. |
20:49 | phil_m | sure |
21:03 | jenkins101 | hi! |
21:03 | jenkins101 | I am trying to run tvheadend on the cuboxi but i get a error |
21:03 | jenkins101 | kernel: Alignment trap: not handling instruction edce0b00 at [<000183f8>] |
21:04 | jenkins101 | anyone else seen this? |
21:41 | zuse | i have a cubox-i with geexbox and having the same problem as this guy: http://www.geexbox.org/forum/topic/cubox-i-terminal-access-problem/ is it really not possible to use the Consoles without disabling xbmc? |
21:45 | mal- | did u try it via ssh? |
21:46 | zuse | ssh is working nice, yes. |
21:46 | zuse | but my tv box has no ssh client :-P |
21:47 | mal- | u want to use the console @geexbox? |
21:47 | mal- | right? |
21:48 | zuse | i want to boot geexbox and config things from my TV (because cuboxi is loosing wifi often) |
21:48 | zuse | config things = on bash level |
21:52 | mal- | dunno sorry |
22:57 | mal- | http://cubox-i.cf/files/OpenELEC-Cuboxi.arm-devel-20140424-img.zip image uploaded...thanks sraue |
22:57 | sraue | mal-, thanks :-) |