linux: allow own initramfs to be specified
PATCH 1/1 linux: allow own initramfs to be specified
The initramfs source location is removed from the given Linux kernel configuration at the moment and only filled in again in case BR2 is asked to provide a cpio for that feature.
This patch allows to specify an own location for such an image file.
--- target/linux/Config.in.advanced | 12 ++++++++++++ target/linux/Makefile.in.advanced | 13 +++++++++++++ 2 files changed, 25 insertions(+), 0 deletions(-)
target/linux/Config.in.advanced +12 -0
@@ -429,6 +429,18 @@ config BR2_KERNEL_CONFIG_METHOD default "xconfig" if BR2_MAKE_XCONFIG default "menuconfig" if BR2_MAKE_MENUCONFIG +config BR2_PACKAGE_LINUX_INITRAMFS + string "initramfs source" + depends on BR2_PACKAGE_LINUX + 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. + + Specify a path relative to BR2's root folder. + endmenu choice
target/linux/Makefile.in.advanced +13 -0
@@ -377,6 +377,19 @@ ifeq ($(BR2_PACKAGE_BUSYBOX_INITRAMFS),y) echo "CONFIG_INITRAMFS_ROOT_UID=0" >> $(LINUX26_DIR)/.config echo "CONFIG_INITRAMFS_ROOT_GID=0" >> $(LINUX26_DIR)/.config endif +ifneq ($(BR2_PACKAGE_LINUX_INITRAMFS),) + $(SED) '/CONFIG_INITRAMFS_SOURCE/d' $(LINUX26_DIR)/.config + $(SED) '/INITRAMFS_ROOT_.ID/d' $(LINUX26_DIR)/.config + echo "CONFIG_BLK_DEV_INITRD=y" >> $(LINUX26_DIR)/.config + echo "CONFIG_INITRAMFS_COMPRESSION_GZIP=y" >> $(LINUX26_DIR)/.config + echo "# CONFIG_INITRAMFS_COMPRESSION_NONE is not set" >> $(LINUX26_DIR)/.config + echo "# CONFIG_INITRAMFS_COMPRESSION_BZIP2 is not set" >> $(LINUX26_DIR)/.config + echo "# CONFIG_INITRAMFS_COMPRESSION_LZMA is not set" >> $(LINUX26_DIR)/.config + echo "CONFIG_INITRAMFS_SOURCE=\"$(PWD)/$(BR2_PACKAGE_LINUX_INITRAMFS)\"" >> \ + $(LINUX26_DIR)/.config + echo "CONFIG_INITRAMFS_ROOT_UID=0" >> $(LINUX26_DIR)/.config + echo "CONFIG_INITRAMFS_ROOT_GID=0" >> $(LINUX26_DIR)/.config +endif $(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) oldconfig touch $@
Signature · 1 line
1.6.3.1
PATCH 1/1 linux: allow own initramfs to be specified
Le Mon, 27 Jul 2009 15:45:30 +0200,
Daniel Mack <[email protected]> a ?crit :
Quoted 5 lines
The initramfs source location is removed from the given Linux kernel configuration at the moment and only filled in again in case BR2 is asked to provide a cpio for that feature.
This patch allows to specify an own location for such an image file.
Just curious, what's the use case for this ?
Buildroot already allows to integrate the root filesystem it generated into the initramfs. It seems your patch allows to integrate a different initramfs that the one generated by Buildroot. Is this correct ? If so, what's your use case ?
Thanks!
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 linux: allow own initramfs to be specified
Quoted 7 lines · Thomas Petazzoni
Le Mon, 27 Jul 2009 15:45:30 +0200,
Daniel Mack <[email protected]> a ?crit :Quoted 4 lines
The initramfs source location is removed from the given Linux kernel configuration at the moment and only filled in again in case BR2 is asked to provide a cpio for that feature.
Quoted 8 lines
Quoted 1 line
This patch allows to specify an own location for such an image file.
Just curious, what's the use case for this ?
Buildroot already allows to integrate the root filesystem it generated into the initramfs. It seems your patch allows to integrate a different initramfs that the one generated by Buildroot. Is this correct ? If so, what's your use case ?
Yep, you're right. We should do it that way. I was thinking of offering a way to let a precompiled cpio image become the initramfs of the built kernel, but it is really better to let br2 handle it all.
There are, however, two problems with the existing code.
1) the linux modules are installed unconditionally which we must avoid our case
2) the initramfs target is currently broken
So, forget about this patch, I'll provide two new ones to make this work.
Thanks,
Daniel