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: Sat, 28 Apr 2007 00:47:34 +0100 [thread overview]
Message-ID: <200704280047.35765.paul@codesourcery.com> (raw)
In-Reply-To: <200704280123.36200.alexis.berlemont@free.fr>
> > In theory most of the bits should be there. However I don't have
> > big-endian hardware to test against,
>
> I had a look at the "integrator cp" user guide. This board and the related
> core modules are supposed to be able to work in big endian mode (even if
> some components are not compatible like the Ethernet controller).
Sort-of. The Integrator boards aren't really big-endian, they're a little
endian board with a CPU that can switch endianness.
> Do you know some other big-endian platform ?
There are many big-endian platforms.
> I do not understand one more issue: I do not guess how a real big-endian
> board can be useful. Is it for checking whether the Linux kernel is working
> in such a configuration ?
I have very little confidence in linux actually working in big-endian mode on
an integrator. I'd also expect some of the consequences to switching to
big-endian mode to be non-obvious. Access to real hadware allows you to check
whether you're hitting kernel bugs or qemu bugs.
Paul
next prev parent reply other threads:[~2007-04-27 23:53 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
2007-04-27 23:23 ` Alexis Berlemont
2007-04-27 23:47 ` Paul Brook [this message]
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=200704280047.35765.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 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.