2007-07-08 21:22:18 +02:00
|
|
|
config BR2_TARGET_ROOTFS_INITRAMFS
|
2012-11-06 14:41:48 +01:00
|
|
|
bool "initial RAM filesystem linked into linux kernel"
|
2010-06-26 00:02:27 +02:00
|
|
|
depends on BR2_LINUX_KERNEL
|
2011-09-06 23:16:09 +02:00
|
|
|
select BR2_TARGET_ROOTFS_CPIO
|
2007-07-08 21:22:18 +02:00
|
|
|
help
|
2010-06-26 00:02:28 +02:00
|
|
|
Integrate the root filesystem generated by Buildroot as an
|
|
|
|
|
initramfs inside the kernel image. This integration will
|
|
|
|
|
take place automatically.
|
|
|
|
|
|
2011-09-06 23:16:09 +02:00
|
|
|
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.
|
2010-06-26 00:02:28 +02:00
|
|
|
|
2011-09-06 23:16:09 +02:00
|
|
|
Note that enabling initramfs together with another filesystem
|
2010-06-26 00:02:28 +02:00
|
|
|
formats doesn't make sense: you would end up having two
|
|
|
|
|
identical root filesystems, one embedded inside the kernel
|
2011-09-06 23:16:09 +02:00
|
|
|
image, and one separately.
|
2007-07-08 21:22:18 +02:00
|
|
|
|
2010-06-26 00:02:27 +02:00
|
|
|
comment "initramfs requires a Linux kernel to be built"
|
|
|
|
|
depends on !BR2_LINUX_KERNEL
|
