OpenPOWER buildroot sources https://git.raptorcs.com/git/buildroot/atom?h=2017.05 2013-12-15T15:24:36+00:00 2013-12-15T15:24:36+00:00 Thomas De Schampheleire patrickdepinguin@gmail.com 2013-12-15T12:20:39+00:00 urn:sha1:8da745f04a0e45be17c53b4a1475798d9b300811 This patch lines up the comments of packages that need a Linux kernel to be built by buildroot, to the format: foo needs a Linux kernel to be built Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2013-07-08T12:50:31+00:00 Valentine Barshak gvaxon@gmail.com 2012-10-09T23:34:56+00:00 urn:sha1:391c82efa14d6db253f42616d970dacbe826b7d5 Initramfs compression does not make much sense for the architectures that support compressed kernel images because in this case the data would be compressed twice. This will eventually result in a bigger kernel image and time overhead when uncompressing it. The only reason to use compressed initramfs is to reduce memory usage when the kernel prepares rootfs, and both the unpacked filesystem and initramfs.cpio are present in the memory. Buildroot attempts to force GZIP compression for initramfs, however it doesn't always work because initramfs compression mode depends on RAM disk compression supported by the kernel. Thus, CONFIG_INITRAMFS_COMPRESSION_GZIP depends on CONFIG_RD_GZIP. If CONFIG_RD_GZIP is not set, setting GZIP initramfs compression will have no effect. Besides, the kernel also supports other compression methods, like BZIP2, LZMA, XZ and LZO. Forcing the good old GZIP does not really make much sense any more. This removes initramfs compression settings from Buildroot, so that the default value preset in the kernel config is used, which is CONFIG_INITRAMFS_COMPRESSION_NONE. If initramfs compression is still needed, it can be set in the kernel config (using make linux-menuconfig) Signed-off-by: Valentine Barshak <gvaxon@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2012-11-07T10:48:13+00:00 Arnout Vandecappelle arnout@mind.be 2012-11-06T13:41:48+00:00 urn:sha1:7e61918f9d5d3c5bc1fb435ae9e6c8013cf5ab07 Recent mails on the list show that it is not very clear how to create an initial RAM fs with buildroot. So make this more explicit in the cpio and initramfs help texts. Hopefully this will reduce the /init debugging we have to do. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2011-09-27T20:46:00+00:00 Arnout Vandecappelle (Essensium/Mind) arnout@mind.be 2011-09-06T21:16:09+00:00 urn:sha1:13a3afc536b845e8de8eea9b91bbc6e7430c4566 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> 2010-06-26T05:44:16+00:00 Thomas Petazzoni thomas.petazzoni@free-electrons.com 2010-06-25T22:02:28+00:00 urn:sha1:c2a44f158eedf40be3ab3bc3c76f61fe032d7b34 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2010-06-26T05:43:20+00:00 Thomas Petazzoni thomas.petazzoni@free-electrons.com 2010-06-25T22:02:27+00:00 urn:sha1:93e801470981010d8760db372f511e04481182d0 Closes #2119 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2010-04-09T09:04:36+00:00 Thomas Petazzoni thomas.petazzoni@free-electrons.com 2010-03-10T21:30:06+00:00 urn:sha1:0585241505cfaddc9db6ae92739bdfb5ce5f9794 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>