From: Rob Landley <rob@landley.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Xin Tong <trent.tong@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM testing image
Date: Sun, 01 Dec 2013 11:14:37 -0600 [thread overview]
Message-ID: <1385918077.1974.298@driftwood> (raw)
In-Reply-To: <CAFEAcA_ootjbP+oOAoV_9J2Rn9bf5sK-qrHCzsDRCR7M9BrwuQ@mail.gmail.com> (from peter.maydell@linaro.org on Tue Nov 12 08:30:39 2013)
On 11/12/2013 08:30:39 AM, Peter Maydell wrote:
> On 12 November 2013 14:27, Xin Tong <trent.tong@gmail.com> wrote:
> > Hi
> >
> > I would like to know where i get can 32bit ARM image
>
> For which board?
>
> > with appropriate network driver.
>
> Appropriate for what?
>
> http://people.debian.org/~aurel32/qemu/armel/
> has a simple versatile kernel/initrd/filesystem
> (it's a little old, though).
My aboriginal linux project (http://landley.net/aboriginal/about.html)
is more or less aimed at this.
Every new kernel release I try to have a build with the current kernel
for arm, mips, ppc32, sh4, x86, x86-64, and sparc out before -rc1 hits.
http://landley.net/aboriginal/downloads/binaries
You probably want system-image-armv5l.tar.bz2, that's for the versatile
board. The
./run-emulator.sh script should boot it to a shell prompt.
These images include a native toolchain capable of rebuilding
themselves under themselves, and also building linux from scratch. The
./dev-environment.sh script boots qemu with more memory and 2 gigs of
persistent scratch space mounted on /home (and will even set it up to
call out to the cross compiler via distcc if you've installed the
appropriate stuff on the host). If you just want to jump straight to
the linux from scratch images, they're in the "extras" subdirectory.
The advantage of these is you can easily reproduce them from source, so
they tend to have up to date kernel and busybox versions. (There's no
such thing as an update uClibc version, but I'm switching that to
musl-libc. And I kept the toolchains at the last gplv2 release because
the FSF has gone sort of crazy, http://ellcc.org should have something
I can switch to before too much longer. And yeah, I'm moving the linux
from scratch build script to 7.4, I've just been buried in other todo
items...)
FYI,
Rob
prev parent reply other threads:[~2013-12-01 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:27 [Qemu-devel] ARM testing image Xin Tong
2013-11-12 14:30 ` Peter Maydell
2013-12-01 17:14 ` Rob Landley [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=1385918077.1974.298@driftwood \
--to=rob@landley.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=trent.tong@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).