[U-Boot] [PATCH 2/2] FIT image: use compression = "none" for ramdisks

Simon Goldschmidt sgoldschmidt at de.pepperl-fuchs.com
Mon Jul 30 13:31:00 UTC 2018



On 30.07.2018 15:25, Wolfgang Denk wrote:
> Dear Simon,
> 
> In message <0787afb7-2da1-4eaa-437e-6f7c7582809c at de.pepperl-fuchs.com> you wrote:
>>
>> I'd still argue that the standard example in 'multi.its' should have
>> compression = "none" for the ramdisks.
> 
> OK, this is your position then.  I can only explain where we are
> coming from: in the early days of U-Boot (well, PPCBoot by then)
> resources were much tighter than today - look at the examples in the
> README: a v2.4.4 Linux kernel image would be around 780 kB
> uncompressed or 330 kB compressed.  At this time it was considered a
> waste of resources to have the gzip uncompression code in the boot
> loader and again duplicated in the Linux kernel - so it was omitted
> there and U-Boot would do all uncompression, also of the ramdisks.

Well, my point was that I couldn't see U-Boot ever handling this. But 
this discussion got a bit confused, split into two threads...

> I agree this is not standard any more, but it is still a valid use
> case, I think.  I know, I'm an old man ;-)

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.

However, I don't have a strong opinion on these examples. I'll let the 
maintainers decide :-)


Best regards,
Simon


More information about the U-Boot mailing list