From: Mark Salisbury <mbs@mc.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: ppc LE questions (seeking help hand info pointers)
Date: Thu, 20 Sep 2001 11:42:39 -0400 [thread overview]
Message-ID: <3BAA0E6F.5050503@mc.com> (raw)
I am familiar with the fact that little endian ppc linux is an unpopular
concept, but I would like to discuss it and ask a few questions about it
anyway. I do _NOT_ want to start a flame war, so if you feel the need to
flame me for this, pleas flame me directly offline and do not pollute
the list.
assume I have a valid reason for wanting to run ppc's in LE mode
assume I already have a (non-linux) ppc OS running LE mode (actually
compiles and runs in either mode, which you run depends on which flavor
of our hardware you use) the differences in the code are limited to a
few header files, some startup code and some context switch code.
(to get an idea of the hardware see www.mc.com)
assume I am also aware of the limitations of the chip in LE mode, and
the intended target is 7400+ processors
question 1. are there already existing patch sets (rejected from
mainline inclusion) available for use as a starting point?
question 2. if 1, what is the primary reason for rejection.
question 3. is there a general issue of endian safety in linux (I would
think not) or just in the ppc-specific code?
question 4. assuming I was willing to deliver a clean, complete LE
enabling patch (including devices that are relevant to me), as a compile
time config option and maintain that patch, what would be the primary
obstacle to inclusion in the main line.
thanks for your time,
Mark
--
/*------------------------------------------------**
** Mark Salisbury | Mercury Computer Systems **
** mbs@mc.com | System OS - Kernel Team **
**------------------------------------------------*/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-09-20 15:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 15:42 Mark Salisbury [this message]
2001-09-20 15:58 ` ppc LE questions (seeking help hand info pointers) Tom Rini
2001-09-20 16:07 ` Geert Uytterhoeven
2001-09-20 16:12 ` Tom Rini
2001-09-20 17:10 ` Brad Boyer
2001-09-20 18:32 ` Mark Salisbury
2001-09-20 19:29 ` Holger Bettag
2001-09-20 19:35 ` David Edelsohn
2001-09-20 20:19 ` Mark Salisbury
2001-09-21 1:46 ` Timothy A. Seufert
2001-09-21 3:54 ` Dan Malek
2001-09-21 7:24 ` Geert Uytterhoeven
2001-09-21 7:47 ` Dan Malek
2001-09-21 7:50 ` Geert Uytterhoeven
2001-09-21 8:19 ` Dan Malek
2001-09-21 17:01 ` Ralph Blach
2001-09-21 17:35 ` David Edelsohn
2001-09-21 18:58 ` David Edelsohn
2001-09-21 20:22 ` Dan Malek
2001-09-21 20:29 ` Benjamin Herrenschmidt
2001-09-21 20:42 ` Benjamin Herrenschmidt
2001-09-21 7:22 ` Geert Uytterhoeven
2001-09-21 9:26 ` keyb Giuliano Pochini
2001-09-21 10:38 ` ppc LE questions (seeking help hand info pointers) Ralph Blach
2001-09-20 20:01 ` Tony Mantler
2001-09-20 18:28 ` Mark Salisbury
2001-09-20 19:12 ` Tom Rini
2001-09-20 22:22 ` Dan Malek
2001-09-21 5:45 ` Troy Benjegerdes
2001-09-28 6:37 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2001-09-21 5:28 Albert D. Cahalan
2001-09-21 6:10 ` Dan Malek
2001-09-21 10:59 ` Ralph Blach
2001-09-21 18:48 Albert D. Cahalan
2001-09-22 0:22 ` Timothy A. Seufert
2001-09-22 20:06 ` Albert D. Cahalan
2001-09-24 17:10 ` Mark Salisbury
2001-09-22 14:23 ` Holger Bettag
2001-09-22 20:26 ` Timothy A. Seufert
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=3BAA0E6F.5050503@mc.com \
--to=mbs@mc.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).