<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/fs/initramfs, branch 2018.02.1</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2018.02.1</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2018.02.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2017-11-30T10:50:42+00:00</updated>
<entry>
<title>fs/initramfs: cleanups, enhance comments</title>
<updated>2017-11-30T10:50:42+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2017-11-12T17:45:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=0a49b49e0a7df15347ccf9fa03c618639e9947b9'/>
<id>urn:sha1:0a49b49e0a7df15347ccf9fa03c618639e9947b9</id>
<content type='text'>
rootfs-initramfs is not using the generic fs infrastructure, because
there is virtually nothing to do to build the initramfs image: there is
no actual image to be built to begin with.

The only purpose of rootfs-initramfs is to ensure the rootfs.cpio image
is built and then that the Linux kernel is rebuilt with that rootfs.cpio
as initramfs source.

Using variables of the fs infra like if it were used is misleading. It
looked nice as long as there was the possibility that rootfs-initramfs
would one day use the fs infra. But there's no way that will happen any
time soon.

Furthermore, the linux' rule linux-rebuild-with-initramfs now already
depends on rootfs-cpio by itself, so we need not duplicate this
dependency in rootfs-initramfs.

Still, we want to advertise that the dependency is on rootfs-cpio, so
we get nice dependency graphs (and not expose the internal
linux-rebuild-with-initramfs rule to the users).

So, remove the variables and directly define the rules.

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Cc: Romain Naour &lt;romain.naour@openwide.fr&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>fs: declare phony targets as such</title>
<updated>2015-04-14T08:12:32+00:00</updated>
<author>
<name>Thomas Petazzoni</name>
<email>thomas.petazzoni@free-electrons.com</email>
</author>
<published>2015-04-12T16:37:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=2aef771f6e05d3fd1ea59c2faab986eaa55f28f7'/>
<id>urn:sha1:2aef771f6e05d3fd1ea59c2faab986eaa55f28f7</id>
<content type='text'>
This commit improves the filesystem handling code to declare its
various targets as PHONY when appropriate.

Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
</content>
</entry>
<entry>
<title>linux: remove support of linux26-* targets</title>
<updated>2014-07-29T21:47:03+00:00</updated>
<author>
<name>Thomas De Schampheleire</name>
<email>patrickdepinguin@gmail.com</email>
</author>
<published>2014-07-24T17:49:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=025d4a17298e85e6efad42bdde619e47bb78ba20'/>
<id>urn:sha1:025d4a17298e85e6efad42bdde619e47bb78ba20</id>
<content type='text'>
The linux-* mirror targets of linux26-* have been added a very long time ago
(2010) and linux 2.6 is now considered 'old' anyway. It no longer makes
sense to support these linux26-* targets, so this patch removes them.

This is a simplification introduced in preparation of the kconfig-package
infrastructure.

Signed-off-by: Thomas De Schampheleire &lt;thomas.de.schampheleire@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>fs/initramfs: fix initramfs support</title>
<updated>2014-03-06T22:01:33+00:00</updated>
<author>
<name>Gustavo Zacarias</name>
<email>gustavo@zacarias.com.ar</email>
</author>
<published>2014-03-06T20:55:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=cfd1f70a10da80b78a607b208695218c8396a57d'/>
<id>urn:sha1:cfd1f70a10da80b78a607b208695218c8396a57d</id>
<content type='text'>
On commit a24877586a566e052897e50e6a0c2f53cfb029f TARGETS_ROOTFS was
introduced, however fs/initramfs/initramfs.mk was never updated, hence a
show-targets would be rootfs-initramfs with rootfs-cpio afterwards hence
never rebuilding the kernel with a proper cpio archive since TARGETS is
always before rootfs-* as stated in the commit description.

Signed-off-by: Gustavo Zacarias &lt;gustavo@zacarias.com.ar&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>Config.in files: unification of comments about dependency on Linux kernel</title>
<updated>2013-12-15T15:24:36+00:00</updated>
<author>
<name>Thomas De Schampheleire</name>
<email>patrickdepinguin@gmail.com</email>
</author>
<published>2013-12-15T12:20:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=8da745f04a0e45be17c53b4a1475798d9b300811'/>
<id>urn:sha1:8da745f04a0e45be17c53b4a1475798d9b300811</id>
<content type='text'>
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 &lt;thomas.de.schampheleire@gmail.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>package: remove the empty trailing lines</title>
<updated>2013-09-13T09:10:23+00:00</updated>
<author>
<name>Jerzy Grzegorek</name>
<email>jerzy.grzegorek@trzebnica.net</email>
</author>
<published>2013-09-13T08:30:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=cd2ff4f637774c2bf7b3d3d11b5e138abf85ef15'/>
<id>urn:sha1:cd2ff4f637774c2bf7b3d3d11b5e138abf85ef15</id>
<content type='text'>
Signed-off-by: Jerzy Grzegorek &lt;jerzy.grzegorek@trzebnica.net&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
<entry>
<title>linux: Do not force GZIP initramfs compression</title>
<updated>2013-07-08T12:50:31+00:00</updated>
<author>
<name>Valentine Barshak</name>
<email>gvaxon@gmail.com</email>
</author>
<published>2012-10-09T23:34:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=391c82efa14d6db253f42616d970dacbe826b7d5'/>
<id>urn:sha1:391c82efa14d6db253f42616d970dacbe826b7d5</id>
<content type='text'>
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 &lt;gvaxon@gmail.com&gt;
Acked-by: Arnout Vandecappelle (Essensium/Mind) &lt;arnout@mind.be&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
<entry>
<title>Normalize separator size to 80</title>
<updated>2013-06-07T08:54:54+00:00</updated>
<author>
<name>Jerzy Grzegorek</name>
<email>jerzy.grzegorek@trzebnica.net</email>
</author>
<published>2013-06-06T21:54:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=086f333f39cdbc0762917272e4c9bb87344fb51a'/>
<id>urn:sha1:086f333f39cdbc0762917272e4c9bb87344fb51a</id>
<content type='text'>
Signed-off-by: Jerzy Grzegorek &lt;jerzy.grzegorek@trzebnica.net&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
<entry>
<title>cpio/initramfs: clarify their use in the help text</title>
<updated>2012-11-07T10:48:13+00:00</updated>
<author>
<name>Arnout Vandecappelle</name>
<email>arnout@mind.be</email>
</author>
<published>2012-11-06T13:41:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=7e61918f9d5d3c5bc1fb435ae9e6c8013cf5ab07'/>
<id>urn:sha1:7e61918f9d5d3c5bc1fb435ae9e6c8013cf5ab07</id>
<content type='text'>
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) &lt;arnout@mind.be&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
<entry>
<title>fs/initramfs: refactor with fs/cpio</title>
<updated>2011-09-27T20:46:00+00:00</updated>
<author>
<name>Arnout Vandecappelle (Essensium/Mind)</name>
<email>arnout@mind.be</email>
</author>
<published>2011-09-06T21:16:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=13a3afc536b845e8de8eea9b91bbc6e7430c4566'/>
<id>urn:sha1:13a3afc536b845e8de8eea9b91bbc6e7430c4566</id>
<content type='text'>
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) &lt;arnout@mind.be&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
</feed>
