public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] One little, two little, three little endian...
Date: Fri, 15 Nov 2002 03:41:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805445@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805439@msgid-missing>

Don Dugger wrote:
> Data compatibility is the only real gotcha I can think of and that's just
> a translation issue.  Potentially creating the translation utilities will
> be a problem but I predict it's a smaller problem than coming up with a
> big endian IA64 Linux.

Have you ever tried to import wrong-endian data?

I thought people gave up trying to do that on 16-bit machines.
I've been in more endian flip-flops than I care to remember.
(Olivetti flip-flopped about every 2 years in the early 90s, talk
about customer nightmares...)

Data conversion has to be re-adressed by *every* application
because of padding. I think the work mostly cannot be amortized over
lots of customers.

I agree with david. User space libs need to be migrated from the
desired environment. See how far a per-process approach gets first.

grant


  parent reply	other threads:[~2002-11-15  3:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15  0:52 [Linux-ia64] One little, two little, three little endian Gavin Scott
2002-11-15  1:55 ` David Mosberger
2002-11-15  2:25 ` Don Dugger
2002-11-15  2:28 ` Randolph Chung
2002-11-15  3:41 ` Grant Grundler [this message]
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-105590709805445@msgid-missing \
    --to=grundler@cup.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox