From: Peter Maydell <peter.maydell@linaro.org>
To: Rob Landley <rob@landley.net>
Cc: zhangzhenkai@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] A Question
Date: Thu, 5 May 2011 23:32:36 +0100 [thread overview]
Message-ID: <BANLkTikDz9pNM+oFbOQEpE0chvoCQTe_nQ@mail.gmail.com> (raw)
In-Reply-To: <4DC3211B.7040009@landley.net>
On 5 May 2011 23:13, Rob Landley <rob@landley.net> wrote:
> On 05/05/2011 02:01 AM, Peter Maydell wrote:
>> I'm afraid I don't entirely understand your file naming
>> system there -- it seems to say which architecture the
>> system images are for but not what board?
>
> Exactly. An armv5l root filesystem will run on dozens of boards. You
> need to rebuild the kernel for a specific board, but not the root
> filesystem or toolchain.
Doh, I should have read the readme a bit more carefully. I
usually take "system image" to mean "complete disk image
including bootloader, kernel and initrd as well as rootfs",
which obviously does include the board-specific bits. On the
other hand the readme does say the tarball includes "a kernel"
so in that sense it is board-specific, presumably.
(ARM kernels having alas not yet got to the point where you
can build a single kernel that will boot on everything.)
-- PMM
next prev parent reply other threads:[~2011-05-05 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 15:26 [Qemu-devel] A Question Zhenkai Zhang
2011-05-04 15:46 ` Peter Maydell
2011-05-04 23:16 ` Rob Landley
2011-05-05 7:01 ` Peter Maydell
2011-05-05 22:13 ` Rob Landley
2011-05-05 22:32 ` Peter Maydell [this message]
2011-05-05 23:20 ` Rob Landley
2011-05-05 23:49 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-08-26 14:31 [Qemu-devel] a question Michael Rolnik
2016-08-26 15:42 ` Peter Maydell
2007-02-27 20:49 Marian-Nicolae V. Ion
2007-03-25 18:35 ` Jan Marten Simons
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=BANLkTikDz9pNM+oFbOQEpE0chvoCQTe_nQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=zhangzhenkai@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).