xref: /OK3568_Linux_fs/buildroot/fs/initramfs/Config.in (revision 4882a59341e53eb6f0b4789bf948001014eff981)
1*4882a593Smuzhiyunconfig BR2_TARGET_ROOTFS_INITRAMFS
2*4882a593Smuzhiyun	bool "initial RAM filesystem linked into linux kernel"
3*4882a593Smuzhiyun	depends on BR2_LINUX_KERNEL
4*4882a593Smuzhiyun	select BR2_TARGET_ROOTFS_CPIO
5*4882a593Smuzhiyun	help
6*4882a593Smuzhiyun	  Integrate the root filesystem generated by Buildroot as an
7*4882a593Smuzhiyun	  initramfs inside the kernel image. This integration will
8*4882a593Smuzhiyun	  take place automatically.
9*4882a593Smuzhiyun
10*4882a593Smuzhiyun	  A rootfs.cpio file will be generated in the images/ directory.
11*4882a593Smuzhiyun	  This is the archive that will be included in the kernel image.
12*4882a593Smuzhiyun	  The default rootfs compression set in the kernel configuration
13*4882a593Smuzhiyun	  is used, regardless of how buildroot's cpio archive is
14*4882a593Smuzhiyun	  configured.
15*4882a593Smuzhiyun
16*4882a593Smuzhiyun	  Note that enabling initramfs together with another filesystem
17*4882a593Smuzhiyun	  formats doesn't make sense: you would end up having two
18*4882a593Smuzhiyun	  identical root filesystems, one embedded inside the kernel
19*4882a593Smuzhiyun	  image, and one separately.
20*4882a593Smuzhiyun
21*4882a593Smuzhiyuncomment "initramfs needs a Linux kernel to be built"
22*4882a593Smuzhiyun	depends on !BR2_LINUX_KERNEL
23