From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: add external initramfs options
Date: Wed, 4 Jun 2014 17:45:05 -0300 [thread overview]
Message-ID: <20140604204505.GA19703@arch.cereza> (raw)
In-Reply-To: <5386131B.6090809@mind.be>
Hello Arnout,
On 28 May 06:47 PM, Arnout Vandecappelle wrote:
[..]
> >
> > The path specified can be a cpio archive or a directory, just like
> > the kernel config. The path is specified w.r.t. BRs topdir, and made
> > absolute since the kernel builds in another directory.
>
> This patch does nothing more than update the kernel config. Since you can
> already supply a custom kernel config, I don't think there is much added value
> to moving these options to the buildroot config.
>
> The only feature you add is that the patch can be relative to the buildroot
> directory. Not enough to be relevant, IMHO, especially since the patch adds
> non-negligible complexity.
>
Our software stack includes a kernel with an appended initramfs to take care
of software upgrade and find, check and switch to the "real" rootfs. Both
the initramfs and rootfs are Buildroot-based, but each of them with their
own configuration and history (in separate git repos).
Hence we came up with this solution: the initramfs would live in a different
repo, and after it's built we use this new option to append it in the kernel.
Maybe you have a better idea, and there's a cleaner way to accomplish this
with Buildroot?
Thanks for the feedback!
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2014-06-04 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 21:01 [Buildroot] [RFC/PATCH] linux: add external initramfs options Guido Martínez
2014-05-28 16:47 ` Arnout Vandecappelle
2014-06-04 20:45 ` Ezequiel Garcia [this message]
2014-06-04 22:29 ` Arnout Vandecappelle
2014-06-09 14:09 ` Ezequiel Garcia
2014-06-09 13:34 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140604204505.GA19703@arch.cereza \
--to=ezequiel@vanguardiasur.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox