> The board fixup is a board-specific thing. Are you doing that in your board > configuration? Didn't realize it was board-specific.
> If you have CONFIG_OF_BOARD_SETUP defined (if you don't that probably is the > answer to your missing #define question), you can run > fdt boardsetup > and then > fdt print / > to see what the fixed up tree looks like. No I do not have this defined, when I include it I cannot compile u-boot, errors out like this: common/libcommon.a(cmd_fdt.o): In function `do_fdt': /home/devone/embedded/orbitServer/u-boot-2009.03/common/cmd_fdt.c:437: undefined reference to `ft_board_setup' lib_ppc/libppc.a(bootm.o): In function `boot_body_linux': /home/devone/embedded/orbitServer/u-boot-2009.03/lib_ppc/bootm.c:272: undefined reference to `ft_board_setup' make: *** [u-boot] Error 1 So I'm not sure I want to mess with getting CONFIG_OF_BOARD_SETUP unless I absolutely have to. > You can also run the bootm command step-by-step (some steps may not apply to > your board)... > > bootm start > bootm loados > bootm ramdisk > bootm fdt > bootm bdt > bootm cmdline > bootm prep > > Print out the tree: > fdt print / > > (last step is...) > bootm go I didn't realize I could do this! Thanks! After "bootm start 400000 - 750000" I'm able to do a "fdt print" to see the fdt I passed in, thought for some reason when I run "bootm loados" it never gets past "Uncompressing Kernel Image..." any idea why? It doesn't freeze here when I do "bootm 400000 - 750000". _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
