From: "H. Peter Anvin" <hpa@zytor.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Jan Engelhardt <jengelh@medozas.de>,
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: Wed, 28 May 2008 12:30:29 -0700 [thread overview]
Message-ID: <483DB2D5.8050502@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0805281916480.29522@cliff.in.clinika.pl>
Maciej W. Rozycki wrote:
> On Wed, 28 May 2008, Jan Engelhardt wrote:
>
>> 801586 or 81586, that is the question. Or 80F86.
>
> Hmm, 801586 should be fine as with Intel 80 used to stand for
> microprocessors and 81586 would be confusing as I think 81 was used for
> RAM devices (82 stood for peripherals, BTW). My vote is for 80F86 though,
> with "F" standing for "fast" as in the 74 TTL series. ;)
>
uname reports i686 on these chips. The rest is ridiculous.
-hpa
next prev parent reply other threads:[~2008-05-28 19:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 16:57 [X86] Fix up silly i1586 boot message 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 [this message]
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
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=483DB2D5.8050502@zytor.com \
--to=hpa@zytor.com \
--cc=davej@redhat.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 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.