mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [X86] Fix up silly i1586 boot message.
Date: Fri, 30 May 2008 22:30:39 +0200	[thread overview]
Message-ID: <20080530203039.GA5119@ucw.cz> (raw)
In-Reply-To: <alpine.LNX.1.10.0805291131450.19264@fbirervta.pbzchgretzou.qr>

On Thu 2008-05-29 11:35:08, Jan Engelhardt wrote:
> 
> On Thursday 2008-05-29 02:13, H. Peter Anvin wrote:
> 
> > Maciej W. Rozycki wrote:
> >> > uname reports i686 on these chips.  The rest is ridiculous.
> >> 
> >> Intel started it first with picking up a ridiculous number for the family
> >> ID for the P4 line.  There is no technical justification for not keeping
> >> these numbers consecutive.  Or keeping it at 6 actually if the P4 is meant
> >> to be seen by software as the Pentium Pro and the rest of the P6 gang.
> >
> > Yes, this is what we eventually ended up doing as causing fewest compatibility
> > problems.  For the message in question, it's better to be consistent with
> > uname.
> 
> Then again, should not all of the i?86 names be collapsed,
> much like there is only "sparc" and "sparc64" for
> the actual sparcv7, sparcv8, sparcv9, sparcv9a pseudo-arches
> used in, for example rpm, etc.

They should, but it is too late for that now.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-05-30 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 16:57 Dave Jones
2008-05-28 17:31 ` H. Peter Anvin
2008-05-28 17:34 ` H. Peter Anvin
2008-05-28 17:48 ` Jan Engelhardt
2008-05-28 17:53   ` Maciej W. Rozycki
2008-05-28 18:02     ` Jan Engelhardt
2008-05-28 18:25       ` Maciej W. Rozycki
2008-05-28 19:30         ` H. Peter Anvin
2008-05-29  0:10           ` Maciej W. Rozycki
2008-05-29  0:13             ` H. Peter Anvin
2008-05-29  9:35               ` Jan Engelhardt
2008-05-30 20:30                 ` Pavel Machek [this message]
2009-10-28  3:08             ` Yuhong Bao
2009-10-28  8:30               ` Jan Engelhardt
2009-10-28 14:46                 ` Yuhong Bao
2009-10-28 15:46                 ` Dave Jones
2009-10-29 16:33                   ` Yuhong Bao
2009-10-28  3:39             ` Yuhong Bao
2008-05-28 17:59   ` Dave Jones
2008-05-28 18:11     ` 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=20080530203039.GA5119@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®