On Wed, Jul 21, 2010 at 09:54:59AM -0500, Matthew McClintock wrote: > > On Jul 21, 2010, at 8:09 AM, Simon Horman wrote: > > > On Wed, Jul 21, 2010 at 10:05:18AM +0200, Sebastian Andrzej Siewior wrote: > >> * Matthew McClintock | 2010-07-20 23:42:57 [-0500]: > >> > >>> This patch series adds full support for booting with a flat device tree > >>> with either uImage or elf file formats. Kexec and Kdump should work, and > >>> you should also be able to use ramdisks or reuse your current ramdisk as well > >> > >> just had a brief look and will try to look deeper once I'm able to. One > >> thing I'm not sure is whether we want to introduce the --reuse-initrd > >> option. In my opinion it is just bloat. Yes I know the kernel reserves > >> the region where the initrd is loaded by the boot loader but I'm unsure > >> if we want to keep it that way. We are talking here about 10 MiB which > >> remain unused once the system finished booting. If you kexec you have to > >> specify the kernel, why not the initrd as well? > > > > I tend to agree with Sebastian on this one. > > Well, I think it was already around in the code (git grep > OPT_REUSE_INITRD) in some format so I just made it work. I don't tend to > have an opinion one way or the other, but I can see it being quite useful > for people starting off and don't know how to extract their initrd from > their flash or something like that. Otherwise, there is very little > overhead code wise to have it in there. Point taken. On reflection it seems fine to have the option, its not as if people are forced to use it.
