| To: | Marc Karasek <marc_karasek@ivivity.com> |
|---|---|
| Subject: | Re: Questions? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Thu, 7 Mar 2002 14:07:54 +0100 |
| Cc: | Linux MIPS <linux-mips@oss.sgi.com> |
| In-reply-to: | <1015435541.3714.33.camel@MCK_Linux>; from marc_karasek@ivivity.com on Wed, Mar 06, 2002 at 12:25:11PM -0500 |
| References: | <1015435541.3714.33.camel@MCK_Linux> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Wed, Mar 06, 2002 at 12:25:11PM -0500, Marc Karasek wrote: > > How many of you are involved with embedded linux development using a > MIPS processor? > > What endianess have you chosen for your project and why? > > If you have not guessed it, I am involved with a MIPS/Linux embedded > project and we are trying to determine if there are any pros or cons in > one endianess over the other. The MIPS ABI only covers big endian systems - every "real" MIPS UNIX system is big endian. Everything else is a GNU extension. There is hardly any reason to choose a particular byteorder as usually endianess swapping takes so little CPU time that it isn't even meassurable but so I'm told there are exceptions. If portability of software you're going to write wrt. external data representation (disk or network) is of any importance then I suggest you use a system of the opposite endianess which trip problems much faster. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Questions?, Dominic Sweetman |
|---|---|
| Next by Date: | Re: Questions?, Geert Uytterhoeven |
| Previous by Thread: | Re: Questions?, Dominic Sweetman |
| Next by Thread: | Re: Questions?, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |