IRC log of #cubox of Tue 04 Nov 2014. All times are in CET < Back to index

08:15 rabeeh__ http://blog.ecservices.de/2014/11/03/project-ignition/
10:04 Exaga rabeeh__: i need to learn german :D
10:06 jnettlet Exaga, don't pander to them. They are only 13% of the European population. If they want a bigger target market they should write it in English
11:13 topi` if I go with mainline kernel (3.17) instead of the i.MX6-patched 3.14, what drivers am I going to miss?
11:14 topi` probably hw video decoding at least
12:56 topi` running "make" on the 3.14 imx6 tree yields a file "Image" in arch/arm/boot ... what kind of image is this one? there used to be an uImage
12:56 topi` that you could just copy to /boot
13:01 Artox topi`: actually wou will want a zImage
13:01 Artox the command I usually run is this: make zImage dtbs modules
13:02 topi` Artox: I thought uBoot requires the uImage which contains the headers for uboot
13:02 Artox with 3.14 kernel you use zImage and devicetree
13:02 Artox so you need zImage and the right .dtb's
13:02 Artox uboot can guess things too
13:02 Artox like detecting file end
13:02 topi` ok
13:03 topi` so, zImage just goes to /boot ?
13:03 topi` is there a HOWTO on this that is up to date?
13:03 Artox I dont think so
13:06 topi` have you tried the mainline kernel? what features will be missing? (Video decode probably)
15:01 topi` what do I do with the .dtb files? should I just place them in /boot ?
15:01 topi` the "Building the kernel" guide on cubox wiki pages does not talk about that at all
15:11 joelbaby topi` they go into boot along with zImage
15:11 joelbaby and uEnv.txt
15:11 topi` I put it there, but now I get this:
15:11 topi` ** Unable to read file /imx6q-hummingboard.dtb **
15:11 topi` WARN: Cannot load the DTB and boot file is type zImage
15:11 topi` (that path doesn't seem right, shouldn't it be /boot/imx6q...
15:11 jnettlet topi`, that is fine. it first looks in / of the first partition and then tries /boot
15:12 topi` the first partition is the boot partition (it's a VFAT)
15:14 topi` ok the filenames don't match
15:14 topi` -rw-r--r-- 1 topi topi 33568 Nov 4 14:07 imx6q-cubox-i.dtb
15:14 topi` -rw-r--r-- 1 topi topi 355 Nov 4 14:07 imx6q-cubox-i.dts
15:14 topi` I have THESE on my /boot ... should I rename them?
15:14 topi` and why is there two of them :)
15:14 jnettlet because you copied too much
15:14 topi` so I only need the .dtb?
15:14 jnettlet you don't want the .dts files
15:15 topi` we need a Wiki entry that tells the newbies that we don't need them...
15:15 jnettlet and you need the hummingboard files
15:15 topi` not cubox?
15:16 jnettlet do you have a cubox or hummingboard?
15:16 topi` a humming
15:16 topi` so they have different device layouts?
15:16 jnettlet It is all explained here. http://www.solid-run.com/wiki/index.php?title=Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard
15:16 topi` I located the *humming* dtb and copied it to boot, let me try again
15:16 joelbaby i think the files it needs are already stated on this page:http://www.solid-run.com/wiki/Building_the_kernel_and_u-boot_for_the_CuBox-i_and_the_HummingBoard
15:17 topi` I have exactly that wiki page open
15:17 topi` I've read it several times, but nowhere does it say what to DO with those .dtb files...
15:17 topi` sorry guys
15:17 topi` maybe I'm blind...
15:17 joelbaby and scroll to where it says "The generated files are -"
15:19 topi` yeah. well, it didn't tell where they should go
15:19 topi` the file names seemed way too long for a FAT file system...
15:20 topi` damn, I get nothing on HDMI, and no serial console either... I guess for the serial I need to specify console=ttymcx0 in the uenv.txt
15:20 topi` ah, framebuffer works, my stupid display just had gone into some hibernate
15:21 topi` X11 doesn't start anymore :)
15:21 topi` (I'm using that old debian/jessie image from january...)
15:21 jnettlet this is with the 3.14.14 kernel?
15:22 jnettlet you need to make sure that you have the latest non-beta gpu drivers
15:22 topi` yeah maybe the DRM conflicts with the newer kernel
15:29 topi` this 3.14 kernel feels a lot more responsive and doesn't suffer from odd lockups
15:29 topi` thanks guys, great work!
15:32 topi` hm, there's a kernel task called "Vivante Kernel" ... sounds dangerous. I hope it doesn't want to crash my kernel.
15:35 jnettlet your welcome
15:55 topi` next steps, gstreamer... I already installed gstreamer-1.0 and plugins, how do I get the i.mx6 specific back end?
15:56 topi` found the Tiny Devices blog, let's see
16:14 topi` where do I get libfslvpuwrap ?
16:15 iii hey guys
16:15 iii a few questions, is the cubox i2 overclockable ?
16:23 topi` iii: I haven't tried. but I hear the i.MX6 solo can be clocked up to 1.2 ghz
16:25 iii oh.
16:26 iii For using with XBMC, what diff. in speed should I expect from the i2 vs i2ex ? Especially the use of plugins (I'm not talking about video, which is accelerated anyhow).
16:33 topi` dunno, if you have good altivec-accelerated plugins, then it's probably the same
16:33 topi` since you're going to hit the memory bus bandwidth limits anyway
16:48 crazystick I've been working on getting i2c working on the Hummingboard i2eX under Arch. I found this forum post which described the things that needed adding to the dtsi files. I patched it and rebuilt the dtb files, and it is working.
16:49 crazystick My question is how does this get into the SR kernel on github?
16:52 crazystick Oh, the forum post is here: http://www.solid-run.com/community/topic1571.html
16:52 crazystick last post has the working i2c bits
18:09 iii you mean I won't be hitting the memory bandwitdh limit on either boards..
18:09 iii which plugins use altivec ?
18:15 iii also, wouldn't it benfit from the extra memory ?
18:58 Exaga jnettlet: Du Hast ya 'ne Macke :>
19:14 jnettlet Exaga, nein