linux-kernel - Re: [X86] Fix up silly i1586 boot message.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <483DB2D5.8050502@zytor.com>
Date:	Wed, 28 May 2008 12:30:29 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
CC:	Jan Engelhardt <jengelh@...ozas.de>, Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [X86] Fix up silly i1586 boot message.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/