[Qemu-devel] ARM testing image

[Qemu-devel] ARM testing image

[Xin Tong]

[-- Attachment #1: Type: text/plain, Size: 106 bytes --]

Hi

I would like to know where i get can 32bit ARM image with appropriate
network driver.

thank you,
Xin

[-- Attachment #2: Type: text/html, Size: 667 bytes --]

Re: [Qemu-devel] ARM testing image

[Peter Maydell]

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).

-- PMM

Re: [Qemu-devel] ARM testing image

[Rob Landley]

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