BLK_DEV_INITRD: do not require BLK_DEV_RAM=y
Subsystems (2)
Hello,
Initramfs initrd images do not need a ramdisk device, so remove this restriction in Kconfig. BLK_DEV_RAM=n saves about 13k on i386. Also without ramdisk device there's no need for "dry run", so initramfs unpacks much faster.
People using cramfs, squashfs, or gzipped ext2/minix initrd images are probably smart enough not to turn off ramdisk support by accident.
Signature · 1 line
Zdenek Pavlas
drivers/block/Kconfig +0 -1
@@ -400,7 +400,6 @@ config BLK_DEV_INITRD bool "Initial RAM disk (initrd) support" - depends on BLK_DEV_RAM=y help The initial RAM disk is a RAM disk that is loaded by the boot loader (loadlin or lilo) and that is mounted as root before the normal boot
init/initramfs.c +10 -0
@@ -484,6 +484,7 @@panic (err);#ifdef CONFIG_BLK_DEV_INITRD if (initrd_start) { +#ifdef CONFIG_BLK_DEV_RAM int fd;printk (KERN_INFO "checking if image is initramfs..." ); err = unpack_to_rootfs((char *)initrd_start,
@@ -503,6 +504,15 @@sys_close (fd);free_initrd (); } +#else +printk (KERN_INFO "Unpacking initramfs..." ); + err =unpack_to_rootfs ((char *)initrd_start, + initrd_end - initrd_start,0 ); +if (err) +panic (err); +printk (" done\n" ); +free_initrd (); +#endif }#endif }