* Ming Lei <tom.leiming@xxxxxxxxx> [130603 08:34]: > Hi, > > On Sat, May 18, 2013 at 3:17 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > We can now boot with device tree. If you don't want to update u-boot, > > you can boot with appended DTB with the following instructions: > > > > 1. Make sure you have the appended DTB support in .config > > > > CONFIG_ARM_APPENDED_DTB=y > > CONFIG_ARM_ATAG_DTB_COMPAT=y > > CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y > > > > 2. Build the zImage > > > > $ ARCH=arm CROSS_COMPILE=... make zImage > > > > 3. Build the device tree blobs > > > > $ ARCH=arm CROSS_COMPILE=... make dtbs > > > > 4. Append the correct panda dtb to zImage > > > > Depending on your hardware it's omap4-panda.dtb, omap4-panda-a4.dtb > > or omap4-panda-es.dtb. > > > > $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap4-panda-es.dtb > /tmp/appended > > > > 5. Use mkimage to produce the appended device tree uImage > > > > $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \ > > -n "Linux" -d /tmp/appended /tmp/uImage > > I followed the above steps and tried devicetree on Pandaboard against > 3.10.0-rc3-next-20130528, and the board will hang during boot, but works > well with legacy mode. > > Hardware: Pandaboard A1 > dtb: omap4-panda.dtb > > See 'dmesg' on below link: > > http://kernel.ubuntu.com/~ming/up/panda-dts.dmesg > Hmm looks like it boots to init. Maybe add initcall_debug to the cmdline in case there's some late_initcall that causes the issue. It's probably some trivial issue causing it. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
