Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Dan Malek <dan@embeddededge.com>
Cc: JP Foster <jp.foster@exterity.co.uk>, linux-mips@linux-mips.org
Subject: Re: Big Endian au1550
Date: Wed, 23 Feb 2005 15:06:17 +0000	[thread overview]
Message-ID: <20050223150617.GA18290@linux-mips.org> (raw)
In-Reply-To: <cb80abe539fa80effd786cacc1340de7@embeddededge.com>

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

  reply	other threads:[~2005-02-23 15:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 11:22 Big Endian au1550 JP Foster
2005-02-23 11:23 ` Ralf Baechle
     [not found] ` <000301c5199d$3154ad40$0300a8c0@Exterity.local>
2005-02-23 12:05   ` JP Foster
2005-02-23 13:17     ` Ralf Baechle
2005-02-23 15:03     ` Dan Malek
2005-02-23 15:06       ` Ralf Baechle [this message]
2005-02-23 17:02         ` Dan Malek
2005-03-04 20:23           ` Ralf Baechle
2005-03-04 20:44             ` Dan Malek
2005-02-23 16:57       ` Thomas Sailer
2005-02-23 17:47         ` Pete Popov
     [not found]         ` <000001c519d1$84d9c250$0300a8c0@Exterity.local>
2005-02-24 10:04           ` JP Foster
2005-02-24 16:15             ` Peter Popov
2005-02-24 17:09               ` JP Foster
2005-02-25 17:29               ` JP Foster
2005-02-24 16:19             ` Clem Taylor
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 18:30 Prashant Viswanathan
2005-04-28  2:14 Prashant Viswanathan
2005-04-28  2:23 ` Manish Lachwani
2005-04-28  3:44 Prashant Viswanathan
2005-04-28  3:57 ` ppopov
2005-04-28  8:56   ` JP
2005-04-28 18:18 Prashant Viswanathan

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=20050223150617.GA18290@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dan@embeddededge.com \
    --cc=jp.foster@exterity.co.uk \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox