From: Pete Popov <ppopov@embeddedalley.com>
To: Thomas Sailer <sailer@scs.ch>
Cc: Dan Malek <dan@embeddededge.com>,
JP Foster <jp.foster@exterity.co.uk>,
linux-mips@linux-mips.org
Subject: Re: Big Endian au1550
Date: Wed, 23 Feb 2005 09:47:22 -0800 [thread overview]
Message-ID: <421CC1AA.4070201@embeddedalley.com> (raw)
In-Reply-To: <1109177856.18018.13.camel@kronenbourg.scs.ch>
Thomas Sailer wrote:
> On Wed, 2005-02-23 at 10:03 -0500, Dan Malek wrote:
>
>
>>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.
>
>
> Last time I tried (about a month ago using the then current linux-mips
> 2.6 CVS tree), USB host didn't work neither in big nor little endian
> mode on my AMD Pb1000. Ethernet and Serial worked either way.
We've been doing all the 2.6 work on the Db1x boards. The Pb1x need
an uplift as well, but I don't know if we'll have time to do it.
Pete
next prev parent reply other threads:[~2005-02-23 17:47 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
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 [this message]
[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=421CC1AA.4070201@embeddedalley.com \
--to=ppopov@embeddedalley.com \
--cc=dan@embeddededge.com \
--cc=jp.foster@exterity.co.uk \
--cc=linux-mips@linux-mips.org \
--cc=sailer@scs.ch \
/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.