From: Rob Landley <rob@landley.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Arm big endian?
Date: Thu, 3 Jun 2010 18:25:03 -0500 [thread overview]
Message-ID: <201006031825.04344.rob@landley.net> (raw)
In-Reply-To: <201006030852.03792.paul@codesourcery.com>
On Thursday 03 June 2010 02:52:03 Paul Brook wrote:
> > I'm trying to get arm big endian support to work. I patched the 2.6.33
> > kernel to pretend that good old versatilepb can have a big endian CPU
> > plugged into it (attached), and then I built a kernel with the attached
> > .config, and qemu went "boing":
>
> That's about the result I'd expect. The fact that neither qemu nor linux
> claim to support big-endian mode for this hardware should be your first
> clue.
Understood. I there a better emulation to try?
When you say "this hardware" do you mean the board, or do you mean big endian
arm as a CPU? Because there _is_ a qemu-armeb. There isn't a qemu-system-
armeb that I'm aware of, but I thought it autodetected endianness at least for
the CPU...)
If it's the board, I did that because versatilepb has essentially been the
generic board emulation I've plugged all the other arm variants into. There
isn't a -M ip4xx that I'm aware of. (I can try configuring a kernel with just
serial console and see if I can get that to boot, and then add back net and
disk and such one at a time, if that might be a reasonable approach...)
> > Does this look more like a kernel error, or a qemu error?
>
> Probably both.
If I could just get them to agree, I'd be happy. I just want a setup that can
run a big endian arm userspace under system emulation (with network, serial
console, clock, and disk). Emulating a feasible board would be a nice bonus,
but not actually a goal.
> Paul
Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
prev parent reply other threads:[~2010-06-03 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 2:25 [Qemu-devel] Arm big endian? Rob Landley
2010-06-03 7:52 ` Paul Brook
2010-06-03 23:25 ` 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=201006031825.04344.rob@landley.net \
--to=rob@landley.net \
--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 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).