at the risk of asking a dumb question, is there any fundamental
difference between the "retain_initrd" versus "keepinitrd" boot time
parameters?
"retain_initrd" appears to be architecture-independent, and is
handled within init/initramfs.c:
===============
#ifdef CONFIG_BLK_DEV_INITRD
...
if (do_retain_initrd)
goto skip;
...
free_initrd_mem(initrd_start, initrd_end);
skip:
===============
whereas "keepinitrd" is recognized only by arm and avr32, but sure
looks like it does the same thing:
==============
#ifdef CONFIG_BLK_DEV_INITRD
static int keep_initrd;
void free_initrd_mem(unsigned long start, unsigned long end)
{
if (!keep_initrd)
free_area(start, end, "initrd");
}
static int __init keepinitrd_setup(char *__unused)
{
keep_initrd = 1;
return 1;
}
__setup("keepinitrd", keepinitrd_setup);
#endif
==============
if they represent the same thing, it would seem to make sense to
just drop support for "keepinitrd", no?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ
