linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linuxppc-embedded@lists.linuxppc.org, cort@fsmlabs.com,
	Alexandre.Nikolaev@matrox.com
Subject: Re: ppc little-endian port
Date: Mon, 30 Apr 2001 18:44:12 -0400	[thread overview]
Message-ID: <3AEDEABC.F288060C@mvista.com> (raw)
In-Reply-To: 200104302214.f3UMEsn143131@saturn.cs.uml.edu


"Albert D. Cahalan" wrote:

> Huh? This is the linuxppc-embedded list if I'm not mistaken.

Well, it was originally created for developers to discuss embedded
PowerPC Linux kernel issues.  It wasn't appropriate to discuss that
on the workstation list, although some of us participate on all lists
to ensure nothing is missed.  This list has since turned into a support
desk function, which isn't the intention.

> Do you mean that this discussion belongs on a list where the
> workstation developers can participate?

No, not even there.  There are developer lists for tools, libraries
and applications.  You need to find the places where the developers
for the compilers, binutils, libraries and such hang out.  We seldom
discuss any of that here, unless there is some kernel interface issue
that has to be coordinated with them.


> Dropping little-endian would seriously piss off Motorola's #2
> customer for high-end PowerPC chips.

...and who may that be?  A #2 customer should have high visibility
here (and I've seen the list, so I would like to know where people
really think they are on it).

> The normal order of the world is little-endian, given the
> dominance of PCI and PC data formats. Big-endian is a mistake
> that won't die because it was written into network standards.

You don't get out much, do you :-)?  Lighten up a little, this
is supposed to be fun.......We could argue all day, but there was
lots of computer work done before PCI and PCs.  I'm more than old
enough to know, so just leave it at that.......


	-- Dan

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

  reply	other threads:[~2001-04-30 22:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28 23:16 ppc little-endian port Albert D. Cahalan
2001-04-30 17:15 ` Dan Malek
2001-04-30 18:15   ` Ralph Blach
2001-04-30 20:38     ` Cort Dougan
2001-04-30 22:14   ` Albert D. Cahalan
2001-04-30 22:44     ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-25 12:16 Zehetbauer Thomas
2001-04-23 18:58 Alexandre Nikolaev
2001-04-24  0:15 ` Cort Dougan
2001-04-24  2:47   ` Dan Malek
2001-04-24 10:11     ` Gabriel Paubert
     [not found] ` <3AE5595C.74644FE5@raleigh.ibm.com>
2001-04-24 14:38   ` Alexandre Nikolaev

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=3AEDEABC.F288060C@mvista.com \
    --to=dan@mvista.com \
    --cc=Alexandre.Nikolaev@matrox.com \
    --cc=acahalan@cs.uml.edu \
    --cc=cort@fsmlabs.com \
    --cc=linuxppc-embedded@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).