From: "M. Warner Losh" <imp@bsdimp.com>
To: paul@codesourcery.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM ethernet fixes
Date: Sun, 18 Dec 2005 13:31:43 -0700 (MST) [thread overview]
Message-ID: <20051218.133143.127771894.imp@bsdimp.com> (raw)
In-Reply-To: <200512181753.40316.paul@codesourcery.com>
In message: <200512181753.40316.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
: > Given all these improvements in arm support, what's the status of
: > system level support for arm, and what system is emulated?
:
: Short answer is it should work. A default linux kernel config doesn't quite
: work because it hangs probing for a non-existant VGA card. Disable the VGA
: console driver and it's fine.
:
: It emulates most of an Arm Integrator/CP board with an arm1026E cpu.
: Available peripherals are two UARTs, and a NIC. More than enough to boot
: linux :-)
Well, I'm hoping to boot FreeBSD/arm on the thing. two uarts and a
nic is more than enough to boot FreeBSD as well :-)
: > You don't need device emulation to do userland stuf...
:
: No, but it's a diskless board. You either run everything off an initrd, or you
: need network.
That's good to know.
Warner
next prev parent reply other threads:[~2005-12-18 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 22:17 [Qemu-devel] ARM ethernet fixes Daniel Jacobowitz
2005-12-15 0:00 ` Paul Brook
2005-12-18 16:51 ` Paul Brook
2005-12-18 17:25 ` Daniel Jacobowitz
2005-12-18 17:42 ` M. Warner Losh
2005-12-18 17:53 ` Paul Brook
2005-12-18 20:31 ` M. Warner Losh [this message]
2005-12-18 17:54 ` Daniel Jacobowitz
2005-12-18 18:50 ` Dave Feustel
2005-12-18 21:57 ` [Qemu-devel] " Antti P Miettinen
2005-12-18 22:29 ` [Qemu-devel] ARM page crossing inside insn? (Re: ARM ethernet fixes) Antti P Miettinen
2005-12-19 9:40 ` [Qemu-devel] " Antti P Miettinen
2005-12-19 15:24 ` Antti P Miettinen
2005-12-19 16:53 ` Daniel Jacobowitz
2005-12-19 19:25 ` Antti P Miettinen
2005-12-26 2:30 ` Antti P Miettinen
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=20051218.133143.127771894.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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.