From: "H. Peter Anvin" <hpa@transmeta.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu detection fixes for test10-pre4
Date: Fri, 27 Oct 2000 13:02:39 -0700 [thread overview]
Message-ID: <39F9DF5F.F5E6E4B8@transmeta.com> (raw)
In-Reply-To: <200010271946.e9RJk6K01211@pincoya.inf.utfsm.cl>
Horst von Brand wrote:
>
> "H. Peter Anvin" <hpa@transmeta.com>said:
> > Alan Cox wrote:
>
> [...]
>
> > > > We should never have used anything but "i386" as the utsname... sigh.
>
> > > Its questionable if we should include the 'i'
>
> > True enough, personally I prefer "x86".
>
> ia32 is the official name. OTOH, i[3-6]86 _are_ different beasts...
>
IA32 is a retcon, and is used only by Intel anyway. There are
differences between the i686 lines that are significantly bigger than
between the i486 and i586, and that doesn't even begin to count non-Intel
chips.
However, changing it to "i386" consistently would still work with
existing software. Using "x86" or "ia32" or "ix86pc" (what Solaris calls
it) would break stuff.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8snfgq$uvr$1@cesium.transmeta.com>
2000-10-27 14:21 ` [PATCH] cpu detection fixes for test10-pre4 Alan Cox
2000-10-27 17:55 ` Tim Riker
2000-10-27 18:43 ` H. Peter Anvin
2000-10-27 19:46 ` Horst von Brand
2000-10-27 20:02 ` H. Peter Anvin [this message]
2000-10-27 20:55 ` Alan Cox
2000-10-27 21:14 ` H. Peter Anvin
2000-10-28 4:32 ` IA-32 (was Re: [PATCH] cpu detection fixes for test10-pre4) Barry K. Nathan
2000-10-28 6:02 ` H. Peter Anvin
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=39F9DF5F.F5E6E4B8@transmeta.com \
--to=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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