From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] multiple kernel build?
Date: Sun, 16 Feb 2020 02:08:19 +0100 [thread overview]
Message-ID: <20200216020819.1dd9ae09@windsurf> (raw)
In-Reply-To: <CAG=Azd9yPUL0hrMnL9xf9J69uwwv4GUqCmMK5RciZDexzSDsiQ@mail.gmail.com>
On Sat, 15 Feb 2020 10:12:12 -0500
Wesley Chow <wes@cortico.ai> wrote:
> I'm having trouble figuring out if buildroot had a mechanism for building
> multiple Linux kernels within one image. For example, if I would like to
> provide one image for different Raspberry Pi versions or QEMU, I would need
> to distribute kernels for different CPU archs (setting aside the problem of
> detecting which hardware I'm on in the bootloader). Is this currently
> possible?
If you need to build multiple kernels, then you need one separate
Buildroot configuration for each. Buildroot is very simple: one
Buildroot configuration allows to build one system, i.e one toolchain,
one kernel, one root filesystem image.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-02-16 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 15:12 [Buildroot] multiple kernel build? Wesley Chow
2020-02-16 1:08 ` Thomas Petazzoni [this message]
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=20200216020819.1dd9ae09@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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