13a3afc536
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>
22 lines
856 B
Plaintext
22 lines
856 B
Plaintext
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.
|
|
|
|
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 another filesystem
|
|
formats doesn't make sense: you would end up having two
|
|
identical root filesystems, one embedded inside the kernel
|
|
image, and one separately.
|
|
|
|
comment "initramfs requires a Linux kernel to be built"
|
|
depends on !BR2_LINUX_KERNEL
|