From: Hollis Blanchard <hollisb@us.ibm.com>
To: Rob Landley <rob@landley.net>
Cc: firmware@them.com, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] endianness and network emulation for PowerPC
Date: Mon, 18 Feb 2008 14:57:57 -0600 [thread overview]
Message-ID: <1203368277.3428.62.camel@basalt> (raw)
I've been debugging network problems in qemu for a week or two, and
there seem to be some pervasive misunderstandings about endianness. I'm
trying to use a big-endian target on a big-endian guest, and this has
exposed a lot of breakage, including qemu's pci-host.h, isa_mmio.c,
rtl8139.c and ne2000.c.
Rob, I noticed that you're using Linux's "ne.c" in your PowerPC PReP
kernel build for qemu, and to my surprise it actually works for me on a
big-endian host! I'm wondering if you chose ne.c because you found the
other network drivers to be broken?
(Actually I believe this is also working by accident: outsw() in Linux
writes big-endian data, which is incorrectly swapped in isa_mmio.c, and
then incorrectly swapped again in ne2000.c.)
--
Hollis Blanchard
IBM Linux Technology Center
next reply other threads:[~2008-02-18 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 20:57 Hollis Blanchard [this message]
2008-02-19 18:05 ` [Qemu-devel] Re: endianness and network emulation for PowerPC Rob Landley
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=1203368277.3428.62.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=firmware@them.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).