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: Fri, 4 Mar 2005 20:23:38 +0000 [thread overview]
Message-ID: <20050304202338.GA14128@linux-mips.org> (raw)
In-Reply-To: <b230ff2324d488cc6e240cee05ca3af0@embeddededge.com>
On Wed, Feb 23, 2005 at 12:02:47PM -0500, Dan Malek wrote:
> >So I guess this would apply to all Alchemy-based platforms and thus I
> >should offer big endian on all of them again?
>
> Yes, big endian should be an option. If it doesn't work, it
> should get fixed :-)
Okay. I don't know which of the Alchemy systems are capable of supporting
big endian at all - some might not due to unavailable firmware for example.
So I guess I'll leave cooking a patch to you or Pete.
Ralf
next prev parent reply other threads:[~2005-03-04 20:24 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 [this message]
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=20050304202338.GA14128@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