From: Joshua Kinard <kumba@gentoo.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
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: Mon, 31 Oct 2011 04:04:17 -0400 [thread overview]
Message-ID: <4EAE5681.2090103@gentoo.org> (raw)
In-Reply-To: <20111030223418.GA16346@alpha.franken.de>
On 10/30/2011 18:34, Thomas Bogendoerfer wrote:
>
> no, but it will make live a lot easier, because address and interrupts don't
> need to be probed by the driver. Right now interrupts are on my todo, since
> there is some weirdness between guiness and fullhouse boxes...
It wouldn't be an SGI machine if it didn't implement something weird or just
plain backwards...
> it still needs something to setup the PCI bus on the card and issue
> the probing. The problem with the Tulip Phobos cards is, that they
> messed up the endianess, so that none of the Linux Tulip drivers will
> work out of the box...
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?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2011-10-31 8:05 UTC|newest]
Thread overview: 6+ 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-30 15:53 ` Florian Tobias Schandinat
2011-10-30 20:43 ` Joshua Kinard
2011-10-30 22:34 ` Thomas Bogendoerfer
2011-10-31 8:04 ` Joshua Kinard [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=4EAE5681.2090103@gentoo.org \
--to=kumba@gentoo.org \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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