All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org, linux-fbdev@vger.kernel.org,
	ralf@linux-mips.org, FlorianSchandinat@gmx.de
Subject: Re: [PATCH v2] GIO bus support for SGI IP22/28
Date: Tue, 01 Nov 2011 10:00:09 +0000	[thread overview]
Message-ID: <20111101100009.GA29087@alpha.franken.de> (raw)
In-Reply-To: <4EAE5681.2090103@gentoo.org>

On Mon, Oct 31, 2011 at 04:04:17AM -0400, Joshua Kinard wrote:
> A.k.a., Tulip (and possibly ThunderLAN) assume little-endian, when we're
> talking big-endian archs here.  Interesting.  Simple fix, as in defining a
> few driver structures with little- and big-endian versions (if they're doing
> something like packing bits or using bitfields)?  Or is it more complex than
> that?

iirc, the PCI bridge on the cards do 32bit swaps (address invariant) so
tulip chips need to run in big endian mode, which in turn makes descriptors
also big endian. But none of the tulip driver supports big endian descriptors.
That's fixable of course.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org, linux-fbdev@vger.kernel.org,
	ralf@linux-mips.org, FlorianSchandinat@gmx.de
Subject: Re: [PATCH v2] GIO bus support for SGI IP22/28
Date: Tue, 1 Nov 2011 11:00:09 +0100	[thread overview]
Message-ID: <20111101100009.GA29087@alpha.franken.de> (raw)
In-Reply-To: <4EAE5681.2090103@gentoo.org>

On Mon, Oct 31, 2011 at 04:04:17AM -0400, Joshua Kinard wrote:
> A.k.a., Tulip (and possibly ThunderLAN) assume little-endian, when we're
> talking big-endian archs here.  Interesting.  Simple fix, as in defining a
> few driver structures with little- and big-endian versions (if they're doing
> something like packing bits or using bitfields)?  Or is it more complex than
> that?

iirc, the PCI bridge on the cards do 32bit swaps (address invariant) so
tulip chips need to run in big endian mode, which in turn makes descriptors
also big endian. But none of the tulip driver supports big endian descriptors.
That's fixable of course.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2011-11-01 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 22:19 [PATCH v2] GIO bus support for SGI IP22/28 Thomas Bogendoerfer
2011-10-20 22:19 ` Thomas Bogendoerfer
2011-10-30 15:53 ` Florian Tobias Schandinat
2011-10-30 15:53   ` Florian Tobias Schandinat
2011-10-30 20:43 ` Joshua Kinard
2011-10-30 20:43   ` Joshua Kinard
2011-10-30 22:34   ` Thomas Bogendoerfer
2011-10-30 22:34     ` Thomas Bogendoerfer
2011-10-31  8:04     ` Joshua Kinard
2011-10-31  8:04       ` Joshua Kinard
2011-11-01 10:00       ` Thomas Bogendoerfer [this message]
2011-11-01 10:00         ` Thomas Bogendoerfer

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=20111101100009.GA29087@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=FlorianSchandinat@gmx.de \
    --cc=kumba@gentoo.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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.