From: Marc Karasek <marc_karasek@ivivity.com>
To: sjhill@cotw.com
Cc: Linux MIPS <linux-mips@oss.sgi.com>
Subject: Re: Questions?
Date: 06 Mar 2002 13:43:25 -0500 [thread overview]
Message-ID: <1015440234.19618.37.camel@MCK_Linux> (raw)
In-Reply-To: <3C865DF6.FFBE3AB@cotw.com>
No, I have been involved with too many sorties in the war already. I
was just asking if there was any issues with one side or the other from
a purely technical aspect.
On Wed, 2002-03-06 at 13:20, Steven J. Hill wrote:
> 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
--
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
678.990.1550 x238
678.990.1551 Fax
*************************/
next prev parent reply other threads:[~2002-03-06 19:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 17:25 Questions? Marc Karasek
2002-03-06 18:20 ` Questions? Steven J. Hill
2002-03-06 18:43 ` Marc Karasek [this message]
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 --
2004-03-31 20:29 Questions! Scott@Charter
2004-03-31 20:36 ` Questions! Bradley Hook
2004-03-31 20:53 ` Questions! Hal Wigoda
2004-03-31 20:39 ` Questions! Hal Wigoda
2004-03-31 21:26 ` Questions! Kevin J. Cummings
2004-03-31 21:40 ` Questions! Hal Wigoda
2004-03-31 21:44 ` Questions! Kevin J. Cummings
2004-03-31 22:05 ` Questions! Christian Mayer
2004-03-31 22:23 ` Questions! Glynn Clements
2004-04-01 7:50 ` Questions! urgrue
2004-04-01 15:27 ` Questions! Hal Wigoda
2004-04-01 16:01 ` Questions! Hisashi T Fujinaka
2004-04-01 16:15 ` Questions! Hal Wigoda
2004-04-01 17:23 ` Questions! Hal Wigoda
2002-03-07 21:44 Questions? Siders, Keith
2002-03-07 19:19 Questions? Siders, Keith
2002-03-07 21:00 ` Questions? Richard Hodges
2002-03-06 20:40 Questions? Marc Karasek
2002-03-06 20:41 ` Questions? Matthew Dharm
2001-01-09 19:28 Questions ? Sara Spencer
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=1015440234.19618.37.camel@MCK_Linux \
--to=marc_karasek@ivivity.com \
--cc=linux-mips@oss.sgi.com \
--cc=sjhill@cotw.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 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.