From: "Steven J. Hill" <sjhill@cotw.com>
To: Marc Karasek <marc_karasek@ivivity.com>
Cc: Linux MIPS <linux-mips@oss.sgi.com>
Subject: Re: Questions?
Date: Wed, 06 Mar 2002 12:20:38 -0600 [thread overview]
Message-ID: <3C865DF6.FFBE3AB@cotw.com> (raw)
In-Reply-To: 1015435541.3714.33.camel@MCK_Linux
Marc Karasek wrote:
>
> How many of you are involved with embedded linux development using a
> MIPS processor?
>
A fair number of us. Over a hundred easily.
> What endianess have you chosen for your project and why?
>
You don't really want to start this holy war, do you? That aside,
usually big endian is more useful in applications moving networking
type traffic or a fair amount of graphics processing. Little endian
is handy if you are porting applications from Windows or a lot of
your software is written in little endian.
That's my $.02.
-Steve
--
Steven J. Hill - Embedded SW Engineer
next prev parent reply other threads:[~2002-03-06 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:25 Questions? Marc Karasek
2002-03-06 18:20 ` Steven J. Hill [this message]
2002-03-06 18:43 ` Questions? Marc Karasek
2002-03-06 18:54 ` Questions? Hartvig Ekner
2002-03-06 18:54 ` Questions? Hartvig Ekner
2002-03-06 19:06 ` Questions? Mike McDonald
2002-03-06 19:44 ` Questions? Matthew Dharm
2002-03-06 20:32 ` Questions? Bradley D. LaRonde
2002-03-07 10:59 ` Questions? Dominic Sweetman
2002-03-07 13:07 ` Questions? Ralf Baechle
2002-03-07 13:11 ` Questions? Geert Uytterhoeven
2002-03-07 13:18 ` Questions? Ralf Baechle
2002-03-07 17:56 ` Questions? Richard Hodges
2002-03-08 9:58 ` Questions? Dominic Sweetman
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 20:40 Questions? Marc Karasek
2002-03-06 20:41 ` Questions? Matthew Dharm
2002-03-07 19:19 Questions? Siders, Keith
2002-03-07 21:00 ` Questions? Richard Hodges
2002-03-07 21:44 Questions? Siders, Keith
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=3C865DF6.FFBE3AB@cotw.com \
--to=sjhill@cotw.com \
--cc=linux-mips@oss.sgi.com \
--cc=marc_karasek@ivivity.com \
/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