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

09:41 jmontleo are patches for recent kernels for the cubox-i available anywhere?
09:43 jnettlet jmontleo, they have been submitted upstream. You should be able to find them on the lkml. There are patches applied to the freescale 3.10 kernel here, https://github.com/linux4kix/linux-imx6/tree/solidrun-imx_3.10.9_1.0.0_alpha
09:44 jmontleo jnettlet, thanks
09:47 jnettlet np
11:52 jnettlet _rmk_, does a .dtb appended the the kernel image always overwrite the one provided by the bootloader? From head.S it looks like yes, but it is not the behavior I am seeing.
11:52 jnettlet or I have been staring at this too long and missing something obvious
12:05 lioka fdt rm /
12:06 lioka helped me on chromebook with mainline kernel
18:17 jnettlet rabeeh, does the eSATA port supply power, or is it a standard eSATA II port?
18:17 jnettlet vs eSATAp
18:58 shakesoda anyone know if adb actually works on the 4.3 cubox-i image
22:58 jmontleo jnettlet, I'm trying to build a kernel for Fedora but all I get is this: http://ur1.ca/gc2c1 If I swap in the uImage from Debian it more or less works. Any idea what I'm missing? This is using rmk's 3.12-rc4 repo, with this config: http://ur1.ca/gc2e8 and doing make bzImage
22:59 jmontleo from there just mkimage -A arm -O linux -T kernel -a 0x10008000 -e 0x10008000 -n Linux-3.10.9-1.0.0-alpha -C none -d zImage uImage and try to boot, but no dice
23:25 _rmk_ jmontleo: first, bzImage doesn't really exist on ARM, but zImage instead
23:26 _rmk_ second, if you're not booting with a separate DT blob, you need to append it to the image and make sure ARM_APPENDED_DTB is enabled in the config