| 00:14 | pask | 'lo i heart about a big problem with DVI screen with cubox ? Is it true ? |
| 00:15 | pask | many people said there is a problem |
| 00:23 | pask | no !!? |
| 01:11 | pask | ... |
| 03:24 | aplund | does anyone have uhs-I working on the 3.10 kernel? |
| 03:24 | aplund | err. the 3.0 kernel |
| 03:24 | aplund | I cannot get it working on the 3.10 kernel, the signal voltage switch doesn't seem to happen right |
| 04:57 | aplund | well... I can see why UMS-1 doesn't work, but I have no idea why. |
| 04:58 | aplund | when the voltage switch command is sent (CMD11) everything seems fine, but the DAT[3:0] bits in the present state register don't go high again. |
| 04:58 | aplund | that is after the clock is turned off and on. |
| 04:59 | aplund | I've tried increasing the delay but that doesn't help |
| 05:00 | aplund | also, does anyone know if this line is right for the pinmux: "MX6QDL_PAD_GPIO_4__SD2_CD_B 0x1b071" |
| 05:00 | aplund | it does seem to make the card detect bits go high |
| 05:01 | aplund | but I don't see the card state stable bit going high. |
| 06:11 | jnettlet | aplund, uhs-I speeds are not supported on CBi. There is a hardware problem that was diagnosed. |
| 06:11 | aplund | jnettlet: as in, it's impossible? |
| 06:12 | jnettlet | aplund, yes without a hardware fix |
| 06:12 | aplund | :( that's a real pain |
| 06:14 | jnettlet | that is why none of the marketing material contains the spec. |
| 06:16 | jnettlet | the new hummingboard will contain the fix. I am not sure what plans are for future CBi's |
| 06:17 | aplund | whats the problem? is it a homebrew fix? |
| 06:18 | jnettlet | depends how good you are at soldering small pins |
| 06:22 | aplund | not great. |
| 08:50 | ralix | morning@all |
| 09:00 | jnettlet | morning ralix |
| 09:03 | ralix | jnettlet, Did you eventually run xbmc Cubox on? If yes under which distro? |
| 09:04 | jnettlet | ralix, I had Cubox running under Xorg on Linaro 12.04, and 12.10 |
| 09:04 | jnettlet | it required a fair amount of patching |
| 09:06 | wbx | jnettlet: what driver do you use for Xorg for cubox-i? |
| 09:07 | wbx | fbdev or is there a driver for the gpu? |
| 09:07 | ralix | At the moment I only have an old Cubox and a utilit�. Smallint (a friend by me) should get his new one. I want the same times to use my Archlinux (as well as my utilte) to test. Too bad you do not have Archlinux;-) |
| 09:07 | jnettlet | wbx, depends which one I am working on. The most used Xorg driver is the one used in Yocto |
| 09:08 | jnettlet | it uses the framebuffer driver, and has accelerated 2d/3d. |
| 09:08 | jnettlet | But it only supports up to Xorg 14.3 I think |
| 09:11 | wbx | jnettlet: and what is the alternative approach? |
| 09:11 | jnettlet | wbx, nothing that is ready for general use yet. |
| 09:12 | wbx | jnettlet: I thought fbdev is 2d only. does the yocto driver provide 3d functionality on top of the standard fbdev driver? |
| 09:12 | ralix | I use at the moment also the fb, and it looks fine ... |
| 09:12 | jnettlet | wbx, Any Xorg driver only supports 2D acceleration. You then need a DRI and Mesa driver that accelerates 3D |
| 09:12 | wbx | jnettlet: and what is required to let the gpu work with xbmc? is xorg needed? |
| 09:12 | jnettlet | Vivante provides binaries for those. |
| 09:13 | jnettlet | to have it work with XBMC right now you actually can't use Xorg. It is only supported on the raw framebuffer. |
| 09:13 | jnettlet | wbx, you can get more complete information from the forums than me. |
| 09:14 | wbx | do I need binary blobs for raw framebuffer? |
| 09:14 | wbx | jnettlet: hey, you are the cubox expert. ;) |
| 09:14 | jnettlet | wbx, well thanks, but I am also busy and lots of other community members have been good enough to document everything in the forums. |
| 09:15 | wbx | jnettlet: what happened to russell? |
| 09:16 | jnettlet | wbx, all the -devel work has moved over to the OFTC server. With the increased userbase we needed a separate channel to focus on drivers/kernel/u-boot work. |
| 09:16 | wbx | which channel? or is it private? |
| 09:17 | jnettlet | OFTC #cubox-devel. It is not private, but it is very focused on dev only discussions. |
| 09:17 | ralix | :) |
| 09:18 | wbx | will dive into the xbmc forum stuff... |
| 09:20 | wbx | still preparing stuff, no hardware arrived, yet. |
| 14:26 | _dab_ | Can someone point me at a site/git that has any patches for the i4pro FEC? Will test/debug anything that stands a chance offixing my bugs. |
| 14:27 | _dab_ | Or is RMKs patch list as good as it gets? |
| 14:59 | Jansmolders86 | Hej guys, I was wondering if any of you had any experience running a webkit browser in kiosk mode on cubox devices. I'm especially interested in the speed in which can handle javascript |
| 18:08 | TwoNotes | When I plug my external hard drive into the Cubox USB port, it seems not to notice. |
| 18:09 | TwoNotes | Yet this same drive works on other systems with same OS, and other USB things (keyboard, thumb drive) are recognized |
| 18:10 | purch | manual mount? which file system? |
| 18:11 | purch | which os in yuor cbox? |
| 18:11 | purch | cubox |
| 18:11 | TwoNotes | Arch Linux. ext4 gfile system |
| 18:11 | TwoNotes | dmesg has zero messages about the new device plgging in |
| 18:12 | TwoNotes | I do not get as far as the mount comand. It is like I never plgged it in |
| 18:12 | purch | does usb drive have external power? |
| 18:13 | TwoNotes | Both USB sockets do work - I connected my keyboard to them and it shows up |
| 18:13 | TwoNotes | The USB drive does spin up, but I tried connecting external power as well - still nothing |
| 18:13 | TwoNotes | It has one of those "Y" cables |
| 18:14 | TwoNotes | The hard drive has ID 14cd:6116 |
| 18:14 | purch | any other usb drive works? |
| 18:15 | TwoNotes | I know the eSATA port works OK - I have another disk working there. |
| 18:15 | TwoNotes | I know a thumb flash drive works ok in the cubox |
| 18:15 | TwoNotes | And this hard drive works on other systems |
| 18:15 | purch | sounds wierd |
| 18:15 | TwoNotes | yes |
| 18:15 | TwoNotes | I am considering getting an eSATA enclosure for this disk so I can connect it that way |
| 18:15 | purch | bad contact in cable? |
| 18:16 | TwoNotes | Same cable works elsewhere |
| 18:17 | TwoNotes | I expect messages like "[14128.142136] usb-storage 1-1.4.4:1.0: USB Mass Storage device detected" |
| 18:18 | TwoNotes | That is what happens when I plug this drive into other computers |
| 18:18 | TwoNotes | All my computers run Arch Linux |
| 18:18 | purch | or any dmesg row atleast |
| 18:18 | TwoNotes | Of course the Cubox has a slighly older kernel version |
| 18:18 | TwoNotes | yeah. EVen a message saying the device is not supported because the ID does not match or something |
| 18:52 | TwoNotes | I recall that one USB port is preferred over the other for hard disks. Which is it? |
| 19:09 | davorin | top one |
| 20:22 | dozn | What's the reason for that? |
| 20:22 | dozn | Trying to figure out if it would affect any other use cases |
| 20:22 | dozn | Available bandwidth? |
| 20:27 | TwoNotes | Higher interrupt priority? |
| 22:39 | alpha_one_x86 | I have start my MMORPG server under cubox-i, and profiled it, it's very interresting, someone wish the result? |