linux-mips
[Top] [All Lists]

Re: Big Endian au1550

To: Dan Malek <dan@embeddededge.com>
Subject: Re: Big Endian au1550
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 23 Feb 2005 15:06:17 +0000
Cc: JP Foster <jp.foster@exterity.co.uk>, linux-mips@linux-mips.org
In-reply-to: <cb80abe539fa80effd786cacc1340de7@embeddededge.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1109157737.16445.6.camel@localhost.localdomain> <000301c5199d$3154ad40$0300a8c0@Exterity.local> <1109160313.16445.20.camel@localhost.localdomain> <cb80abe539fa80effd786cacc1340de7@embeddededge.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Wed, Feb 23, 2005 at 10:03:01AM -0500, Dan Malek wrote:

> >Fair enough. Has anyone got big-endian au1xxx working ever?
> 
> The only issues with big endian Au1xxx is the USB and potentially
> PCI.  There have been recent patches posted for USB that could
> fix this.  The PCI problem is with the read/write/in/out macros.
> They were never written properly and I haven't checked to see
> if this was corrected in 2.6.
> 
> That aside, I have worked on several big endian Au1xxx projects
> that are successful.  I never found a way, aside from #ifdefs for
> byte sex in generic files, to make the same source compile in
> either mode.  It's a fairly low priority on my list of other Au1xxx 
> projects :-)
> 
> The Linux sources have worked, and if they currently don't we
> should fix them.

So I guess this would apply to all Alchemy-based platforms and thus I
should offer big endian on all of them again?

  Ralf

<Prev in Thread] Current Thread [Next in Thread>