Hi, On Sat, Nov 5, 2011 at 11:41 AM, Marek Vasut <marek.va...@gmail.com> wrote: >> image_get_ram_disk() and image_get_kernel() perform operations in a >> consistent order. Modify image_get_fdt() to do things the same way. >> This allows a later change to insert some image header manipulations >> into these three functions in a consistent fashion. >> >> v2: New patch >> >> Signed-off-by: Stephen Warren <swar...@nvidia.com> > > Hi Stephen, > > this patchset is good and all, but can we not also introduce cmd_zload to load > zImages? Wolfgang, today's ARM hardware will really benefit from that, uImage > holds us back a lot these days. Other option is to extend cmd_bootm() to load > zImages. > > Cheers >
Just a quick Q. What is the ultimate intent here? Should we be aiming to have U-Boot copy and decompress the data into RAM ready for Linux? In theory this should be slightly faster since U-Boot already has the data in its cache. I think zImage now supports having an FDT inside but what is the advantage of zImage over a uImage with compressed portions? Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
