Messages in this thread Patch in this message | | | Date | Mon, 05 Mar 2007 23:09:34 +0100 | From | dimitri.gorokhovik@free ... | Subject | [PATCH] initramfs should not depend on CONFIG_BLOCK |
| |
initramfs ended up depending on BLOCK:
INITRAMFS_SOURCE <-- BLK_DEV_INITRD <-- BLOCK
This inhibits use of customized-initramfs-over-ramfs without block layer (ramfs would still be enabled), useful in embedded applications.
Move BLK_DEV_INITRD out of 'drivers/block/Kconfig' and into 'init/Kconfig', make it unconditional.
Signed-off-by: Dimitri Gorokhovik <dimitri.gorokhovik@free.fr>
--- linux-2.6.21-rc2-git4-broken/init/Kconfig 2007-03-05 23:20:27.000000000 +0100 +++ linux-2.6.21-rc2-git4-fixed/init/Kconfig 2007-03-05 22:22:48.000000000 +0100 @@ -304,6 +304,23 @@ config RELAY
If unsure, say N.
+config BLK_DEV_INITRD + bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support" + depends on BROKEN || !FRV + help + The initial RAM filesystem is a ramfs which is loaded by the + boot loader (loadlin or lilo) and that is mounted as root + before the normal boot procedure. It is typically used to + load modules needed to mount the "real" root file system, + etc. See <file:Documentation/initrd.txt> for details. + + If RAM disk support (BLK_DEV_RAM) is also included, this + also enables initial RAM disk (initrd) support and adds + 15 Kbytes (more on some other architectures) to the kernel size. + + If unsure say Y. + if BLK_DEV_INITRD
source "usr/Kconfig" --- linux-2.6.21-rc2-git4-broken/drivers/block/Kconfig 2007-03-05 23:20:21.000000000 +0100 +++ linux-2.6.21-rc2-git4-fixed/drivers/block/Kconfig 2007-03-05 22:22:48.000000000 +0100 @@ -406,21 +406,6 @@ config BLK_DEV_RAM_BLOCKSIZE setups function - apparently needed by the rd_load_image routine that supposes the filesystem in the image uses a 1024 blocksize.
-config BLK_DEV_INITRD - bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support" - depends on BROKEN || !FRV - help - The initial RAM filesystem is a ramfs which is loaded by the - boot loader (loadlin or lilo) and that is mounted as root - before the normal boot procedure. It is typically used to - load modules needed to mount the "real" root file system, - etc. See <file:Documentation/initrd.txt> for details. - - If RAM disk support (BLK_DEV_RAM) is also included, this - also enables initial RAM disk (initrd) support and adds - 15 Kbytes (more on some other architectures) to the kernel size. - - If unsure say Y.
config CDROM_PKTCDVD tristate "Packet writing on CD/DVD media" @@ -472,3 +457,5 @@ config ATA_OVER_ETH endmenu
endif
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |