Hi Olof, Thanks for joining the party here :) On Fri, Jul 18, 2014 at 6:56 AM, Olof Johansson <olof@xxxxxxxxx> wrote: > Anyone got a simple writeup on the steps needed to boot, bl1/2 needed, > expected offset into eMMC for where it goes, etc? https://github.com/hardkernel/u-boot/blob/odroid-v2010.12/sd_fuse/sd_fusing.sh is probably the best "writeup" :) https://github.com/hardkernel/u-boot/tree/odroid-v2010.12/sd_fuse has the blobs needed (they have not changed at all in the U3's history, so the ones you have already will work fine). Samsung guys are also upstreaming support into uboot, including a README.odroid in the last commit with this info: http://patchwork.ozlabs.org/project/uboot/list/?submitter=23519 > I gave the kernel (next-0717) a go here on my U3, and it boots (as you > mention, no USB comes up). Nice. USB works with the later patches floating around. > I do see a few KERN_ERR printks though: > > [ERR] [ 0.000000] L2C: failed to init: -19 This one is fixed with the patch series "Enable L2 cache support on Exynos4210/4x12 SoCs" > [ERR] [ 0.001302] missing device node for CPU 0 > [ERR] [ 0.001344] missing device node for CPU 1 > [ERR] [ 0.001366] missing device node for CPU 2 > [ERR] [ 0.001386] missing device node for CPU 3 Not sure about these - I still get them with all the patches applied. > [ERR] [ 0.156490] max77686 0-0009: irq is not specified I submitted a patch for this, "ARM: dts: Enable PMIC interrupts on ODROID" > [ERR] [ 1.339498] /i2c@13860000/usb3503@08: could not get > #clock-cells for /system-controller@10020000 > [ERR] [ 1.348050] ERROR: could not get clock > /i2c@13860000/usb3503@08:refclk(0) I think these go away with the USB patches floating around. > [ERR] [ 1.383055] max77686-rtc max77686-rtc: max77686_rtc_init_reg: > fail to write controlm reg(-6) > [ERR] [ 1.391108] max77686-rtc max77686-rtc: Failed to initialize RTC reg:-6 Fixed with "ARM: dts: ODROID i2c improvements" Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |