Re: tip: bzip2/lzma now in tip:x86/setup-lzma

Jan Engelhardt
2009-02-18T10:30:12Z

On Wednesday 2009-02-18 10:40, Alain Knaff wrote:
>>
>> I would expect of *module* developers to build their code by means of
>> an out-of-tree directory, thereby not causing regeneration of the
>> vmlinux binary or initramfs image. Even if they stayed within the
>> Linux srctree, they could take a shortcut by explicitly stating the
>> target (`make that/foo.ko`). modpost is still something that takes
>> much more time with allmodconfig than compressing the kernel and/or
>> changed modules over and over.
>
>You are right of course for modules inserted by insmod modprobe. But what
>about people who tune parts that must be compiled-in (VFS layer, etc.), or
>that investigate a bug in a module that only occurs when it is compiled
>into the kernel?

The developer would then most likely just disable compression for
the time being.

>>[second topic]
>> As for me: a separate staging directory that is totally unrelated to
>> the Linux tree, and manually running the cpio command. And not
>> embodying it into the kernel because all bootloaders used so far
>> support reading an extra initramfs image.
>
>Interesting. If that is the case in general, for all developers of embedded
>systems, then we might be able to do away with compression of the built-in
>initramfs altogether, as proposed in the very early versions of my patch.

Even if it is true in general, I would not remove CONFIG_INITRAMFS_SOURCE
and attached logic, unless it were a major burden on the maintainers.
(I am not to quantify whether it is such a burden, or is not.)