> If you just want access to the results of the FDT/ATAG preparation that > bootm does, consider using the bootm subcommands to prepare them, then > normal U-Boot commands to write to NAND. Me again. I rethought and the problem with bootm is that the subfunctions (bootm_linux_fdt/do_bootm_linux) are directly boot the kernel. That means either I copy almost the whole function and delete the kernel_entry-call. Or I move the tag/fdt creation out of bootm-command and create a extra function.
The first way I consider bad because of code duplication - therefore I would take the second path. Any Objections? Regards Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
