Dear Simon, In message <97a1d1e5-4415-4db4-9c77-72023f37b...@de.pepperl-fuchs.com> you wrote: > > It *is* a valid use case. But for current kernels (if compression is > enabled), it might be faster to let the kernel unzip the content > directly to the memory location where it should reside in the end.
This was true a long, long time ago on ARM (and this is where most of the unclean implmentations originate), when U-Boot did not enable caches. With this fixed, it is almost always wrong, because we now have an unnecessary memory copy: U-Boot loads the compressed kernel image to one location in RAM, which then runs and uncompresses the code to another address. Is it not obvious that it would be more efficient if U-Boot did the uncompressing directly? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de For every complex problem, there is a solution that is simple, neat, and wrong. -- H. L. Mencken _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
