qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb: Fix host-side endian bugs in hcd-ehci
Date: Thu, 06 Sep 2012 11:53:15 +0200	[thread overview]
Message-ID: <5048728B.2010902@redhat.com> (raw)
In-Reply-To: <1345604699-24851-1-git-send-email-david@gibson.dropbear.id.au>

On 08/22/12 05:04, David Gibson wrote:
> The EHCI device model is horribly broken for big-endian hosts.  It uses a
> union of 'mmio' a byte array which is as-is as the device's MMIO space
> with the various internal registers.  The IO routines assume that mmio is
> laid out in little-endian order, but everything else in the code accesses
> the register variables directly assuming (host) native endian.
> 
> This fix is fairly ugly - a nicer approach would involve converting
> hcd-ehci to use the new-style memory region .read and .write functions -
> but it's the most minimal fix I can see to apply for the qemu 1.2 release.

Oops.  This one slipped through.  Just found it -- to late for 1.2 --
while wading through my inbox looking for unprocessed stuff.

Doing the real thing instead (i.e. convert memory regions) doesn't look
that horrible though, I think we can put that into stable-1.2.  I'll
send out the patch in a few moments.

cheers,
  Gerd

      reply	other threads:[~2012-09-06  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  3:04 [Qemu-devel] [PATCH] usb: Fix host-side endian bugs in hcd-ehci David Gibson
2012-09-06  9:53 ` Gerd Hoffmann [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=5048728B.2010902@redhat.com \
    --to=kraxel@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --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).