All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Held Bier <lausgans@gmail.com>, linux-parisc@vger.kernel.org
Subject: Re: Little endianness
Date: Tue, 10 Feb 2015 07:56:41 -0800	[thread overview]
Message-ID: <1423583801.2167.17.camel@HansenPartnership.com> (raw)
In-Reply-To: <BLU436-SMTP173A5545802614E9A03A58A97240@phx.gbl>

On Tue, 2015-02-10 at 10:30 -0500, John David Anglin wrote:
> On 2015-02-10 5:31 AM, Held Bier wrote:
> > Hi.
> >
> > Looks like PA-RISC 1.1 added bi-endian support.
> > What about PA-RISC Linux? I know it's big endian.
> > But does it possible to build little endian kernel? If so, how?
> > Is migration to little endian planned? It should be reasonable
> > as it will bring more  compatibility with other Linux world.

What compatibility?  x86 is LE, Arm is Schizophrenic, PPC, Sparc and PA
are BE.  We're required to support the bus standards anyway, so the SCSI
bus is BE and the PCI bus LE by spec.  There's no such thing as a
"compatible" endianness.

> Unlikely.  According to the PA 2.0 arch, implementation of this feature 
> was optional.

I think it was originally designed for some type of LASI system.
There's an endian flip in some of the LASI devices as well.  I think the
original problem was LASI was designed big endian, but the chosen SCSI
processor was designed for LE at that time, so they tried to flip the
processor.  I suspect the reason the feature became optional is that it
caused more problems than it solved.

> Further the PDC/IODC firmware and software tool chains need little 
> endian support.  This
> is a massive amount of work.  So, unless one one decided to create a 
> 64-bit embedded
> PA-RISC processor for mass deployment, it wouldn't be worth the effort.

It's a bit pointless too.  Coping with endianness isn't really an
unsolved OS problem, so it would cost a huge amount, open a large can of
worms and buy us nothing.

James



  reply	other threads:[~2015-02-10 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 10:31 Little endianness Held Bier
2015-02-10 15:30 ` John David Anglin
2015-02-10 15:56   ` James Bottomley [this message]
2015-02-15  6:49     ` lausgans
2015-02-15 16:50       ` James Bottomley
2015-02-16 10:26         ` ⁣ ⁣

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=1423583801.2167.17.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=lausgans@gmail.com \
    --cc=linux-parisc@vger.kernel.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 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.