diff options
| author | Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> | 2011-09-06 23:16:09 +0200 |
|---|---|---|
| committer | Peter Korsgaard <jacmet@sunsite.dk> | 2011-09-27 22:46:00 +0200 |
| commit | 13a3afc536b845e8de8eea9b91bbc6e7430c4566 (patch) | |
| tree | e6c12ef1dc34eb5d70877b6c3c7a880958ddce34 /fs/initramfs/Config.in | |
| parent | 3fac21ef8d794b47f731003b399e704349c54346 (diff) | |
| download | buildroot-novena-13a3afc536b845e8de8eea9b91bbc6e7430c4566.tar.gz buildroot-novena-13a3afc536b845e8de8eea9b91bbc6e7430c4566.zip | |
fs/initramfs: refactor with fs/cpio
An initramfs is in fact the same as a cpio archive, but embedded in
the kernel. So instead of duplicating the cpio infrastructure,
we can simply build images/rootfs.cpio and link that into the
kernel.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'fs/initramfs/Config.in')
| -rw-r--r-- | fs/initramfs/Config.in | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/fs/initramfs/Config.in b/fs/initramfs/Config.in index abb3c0cc0..bbc2ab0b7 100644 --- a/fs/initramfs/Config.in +++ b/fs/initramfs/Config.in @@ -1,20 +1,21 @@ config BR2_TARGET_ROOTFS_INITRAMFS bool "initramfs for initial ramdisk of linux kernel" depends on BR2_LINUX_KERNEL + select BR2_TARGET_ROOTFS_CPIO help Integrate the root filesystem generated by Buildroot as an initramfs inside the kernel image. This integration will take place automatically. - The rootfs.initramfs file generated in the images/ directory - is only a text file describing the contents of the initramfs - in a format understood by the CONFIG_INITRAMFS_SOURCE kernel - configuration option. + A rootfs.cpio file will be generated in the images/ directory. + This is the archive that will be included in the kernel image. + The rootfs in the kernel will always be gzip'ed, regardless + of how buildroot's cpio archive is configured. - Note that enabling initramfs together with other filesystem + Note that enabling initramfs together with another filesystem formats doesn't make sense: you would end up having two identical root filesystems, one embedded inside the kernel - image, and one separatly. + image, and one separately. comment "initramfs requires a Linux kernel to be built" depends on !BR2_LINUX_KERNEL |