From: "Gavin Scott" <gavin@allegro.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] One little, two little, three little endian...
Date: Fri, 15 Nov 2002 00:52:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805439@msgid-missing> (raw)
Hello list,
I want a big endian version of Linux for IPF. Just how crazy am I?
I'm working with a group of customers and software developers who are
migrating away from HP's proprietary MPE/iX operating system on the HPe3000
systems that HP announced the discontinuance of one year ago today. Many of
these people are already using HP-UX to some degree, and most are interested
in the possibility of using Linux in the future.
Of course both MPE/iX and HP-UX are big-endian environments, and many of the
people I talk to would be very interested in having an endian-compatible
Linux that would run on big (i.e. IA-64) HP servers. For this group, x86
compatibility is probably a non-issue.
I'm interested in any comments that come to mind. I'm most interested in
just how complex the task would be from a technical point of view, either to
make the system buildable either way, or possibly supporting a per-process
endian bit (which would be cool, but probably a lot more work).
I'm reasonably familiar with the IA-64 architecture and know most of what
there is to know about PA-RISC.
Thanks,
Gavin
--
Gavin Scott
Vice President
Allegro Consultants, Inc.
gavin@allegro.com
next reply other threads:[~2002-11-15 0:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 0:52 Gavin Scott [this message]
2002-11-15 1:55 ` [Linux-ia64] One little, two little, three little endian David Mosberger
2002-11-15 2:25 ` Don Dugger
2002-11-15 2:28 ` Randolph Chung
2002-11-15 3:41 ` Grant Grundler
2002-11-15 3:50 ` Don Dugger
2002-11-15 4:47 ` Randolph Chung
2002-11-15 13:15 ` Matthew Wilcox
2002-11-15 16:11 ` Mario Smarduch
2002-11-15 16:58 ` David Mosberger
2002-11-15 17:44 ` Rich Altmaier
2002-11-15 17:56 ` Gavin Scott
2002-11-15 17:57 ` Gavin Scott
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=marc-linux-ia64-105590709805439@msgid-missing \
--to=gavin@allegro.com \
--cc=linux-ia64@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.