From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: add external initramfs options
Date: Thu, 05 Jun 2014 00:29:43 +0200 [thread overview]
Message-ID: <538F9DD7.6020102@mind.be> (raw)
In-Reply-To: <20140604204505.GA19703@arch.cereza>
On 04/06/14 22:45, Ezequiel Garcia wrote:
> 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?
Use a custom kernel config, and code the path to the external initramfs in that
custom kernel config instead of in the buildroot config. You can use
$(BASE_DIR)/../initramfs-output-dir if you want to avoid absolute paths in the
config.
Actually, in your case the easiest solution would be to build the kernel
together with the initramfs-buildroot and use the initramfs rootfs instead of
the cpio one. In the real-rootfs-buildroot you don't need to build a kernel.
Or am I missing something?
Regards,
Arnout
>
> Thanks for the feedback!
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-06-04 22:29 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
2014-06-04 22:29 ` Arnout Vandecappelle [this message]
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=538F9DD7.6020102@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.