From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Alexis Berlemont <alexis.berlemont@free.fr>
Subject: Re: [Qemu-devel] ARM Big endian system emulation
Date: Fri, 27 Apr 2007 02:22:43 +0100 [thread overview]
Message-ID: <200704270222.45308.paul@codesourcery.com> (raw)
In-Reply-To: <200704270307.50211.alexis.berlemont@free.fr>
> I have a question concerning the system emulation features : what is
> missing in the implementation of qemu to get a system emulation of a big
> endian ARM1026 target (like qemu-armeb for user emulation) ?
In theory most of the bits should be there. However I don't have big-endian
hardware to test against, and don't know if linux supports big-endian mode on
the hardware qemu emulates.
It's likely that many of the emulated devices get it wrong, because I've never
made the effort to figure out what the correct behavior is.
Paul
next prev parent reply other threads:[~2007-04-27 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:07 [Qemu-devel] ARM Big endian system emulation Alexis Berlemont
2007-04-27 1:22 ` Paul Brook [this message]
2007-04-27 23:23 ` Alexis Berlemont
2007-04-27 23:47 ` Paul Brook
2007-04-28 7:58 ` Lennert Buytenhek
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=200704270222.45308.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=alexis.berlemont@free.fr \
--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 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).