The cirros image was rebuilt against the 3.13.0-83 kernel, drivers e1000e, igbvf...

[packages/trusty/cirros-testvm.git] / cirros-testvm / src-cirros / buildroot-2015.05 / fs / initramfs / Config.in

diff --git a/cirros-testvm/src-cirros/buildroot-2015.05/fs/initramfs/Config.in b/cirros-testvm/src-cirros/buildroot-2015.05/fs/initramfs/Config.in
new file mode 100644 (file)
index 0000000..8ed9f7e
--- /dev/null
+++ b/cirros-testvm/src-cirros/buildroot-2015.05/fs/initramfs/Config.in
@@ -0,0 +1,21 @@
+config BR2_TARGET_ROOTFS_INITRAMFS
+       bool "initial RAM filesystem linked into 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 default rootfs compression set in the kernel configuration
+         is used, 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 needs a Linux kernel to be built"
+       depends on !BR2_LINUX_KERNEL