linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: flar@pants.nu (Brad Boyer)
To: trini@kernel.crashing.org (Tom Rini)
Cc: geert@linux-m68k.org (Geert Uytterhoeven),
	mbs@mc.com (Mark Salisbury),
	linuxppc-dev@lists.linuxppc.org (Linux/PPC Development)
Subject: Re: ppc LE questions (seeking help hand info pointers)
Date: Thu, 20 Sep 2001 10:10:01 -0700 (PDT)	[thread overview]
Message-ID: <20010920171002.37DCA2B54A@marcus.pants.nu> (raw)
In-Reply-To: <20010920091221.H13721@cpe-24-221-152-185.az.sprintbbd.net> from "Tom Rini" at Sep 20, 2001 09:12:21 AM


Tom Rini wrote:
> On Thu, Sep 20, 2001 at 06:07:48PM +0200, Geert Uytterhoeven wrote:
> > On Thu, 20 Sep 2001, Tom Rini wrote:
> > > On Thu, Sep 20, 2001 at 11:42:39AM -0400, Mark Salisbury wrote:
> > > > 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.
> > >
> > > The objection to being an arch that attempts to support both LE and BE.
> >
> > Note that we already have a precedent: mips and mipsel, both in arch/mips/.
>
> And SH too, iirc.  I know it can be done.  But do we want to do it is the
> question.

At least in the case of SH, there's a good reason. There's an external pin
that controls the native endianness of the processor, and most setups just
have it forcibly pulled high or low. I suspect the MIPS is the same reason,
since it's used in similar situations. We don't have that excuse with ppc.
Someone would have to come up with an excuse along the lines of "existing
hardware won't work unless we do this" like it would have been for SH.
(I had to work with the SH4e as used by Sega in the Dreamcast...)

	Brad Boyer
	flar@allandria.com


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-09-20 17:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 15:42 ppc LE questions (seeking help hand info pointers) Mark Salisbury
2001-09-20 15:58 ` Tom Rini
2001-09-20 16:07   ` Geert Uytterhoeven
2001-09-20 16:12     ` Tom Rini
2001-09-20 17:10       ` Brad Boyer [this message]
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=20010920171002.37DCA2B54A@marcus.pants.nu \
    --to=flar@pants.nu \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mbs@mc.com \
    --cc=trini@kernel.crashing.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).