qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ne2000: mark I/O as LITTLE_ENDIAN
Date: Wed, 4 Sep 2013 10:39:12 +0200	[thread overview]
Message-ID: <20130904083912.GC8031@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1378120234-14062-1-git-send-email-aurelien@aurel32.net>

On Mon, Sep 02, 2013 at 01:10:34PM +0200, Aurelien Jarno wrote:
> Now that the memory subsystem is propagating the endianness correctly,
> the ne2000 device should have its I/O ports marked as LITTLE_ENDIAN, as
> PCI devices are little endian.
> 
> This makes the ne2000 NIC to work again on PowerPC.
> 
> Cc: qemu-stable@nongnu.org
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> ---
>  hw/net/ne2000.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/net/ne2000.c b/hw/net/ne2000.c
> index 31afd28..c961258 100644
> --- a/hw/net/ne2000.c
> +++ b/hw/net/ne2000.c
> @@ -693,7 +693,7 @@ static void ne2000_write(void *opaque, hwaddr addr,
>  static const MemoryRegionOps ne2000_ops = {
>      .read = ne2000_read,
>      .write = ne2000_write,
> -    .endianness = DEVICE_NATIVE_ENDIAN,
> +    .endianness = DEVICE_LITTLE_ENDIAN,
>  };

This is also used by hw/net/ne2000-isa.c:isa_ne2000_realizefn().  Is it
correct to explicitly say little-endian there?

  reply	other threads:[~2013-09-04  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 11:10 [Qemu-devel] [PATCH] ne2000: mark I/O as LITTLE_ENDIAN Aurelien Jarno
2013-09-04  8:39 ` Stefan Hajnoczi [this message]
2013-09-06 15:28   ` Stefan Hajnoczi

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=20130904083912.GC8031@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).