From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755495AbYE2AOS (ORCPT ); Wed, 28 May 2008 20:14:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752241AbYE2AOK (ORCPT ); Wed, 28 May 2008 20:14:10 -0400 Received: from terminus.zytor.com ([198.137.202.10]:35766 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752146AbYE2AOJ (ORCPT ); Wed, 28 May 2008 20:14:09 -0400 Message-ID: <483DF520.6010602@zytor.com> Date: Wed, 28 May 2008 17:13:20 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: "Maciej W. Rozycki" CC: Jan Engelhardt , Dave Jones , Linux Kernel , Ingo Molnar , Thomas Gleixner Subject: Re: [X86] Fix up silly i1586 boot message. References: <20080528165713.GA412@redhat.com> <483DB2D5.8050502@zytor.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -hpa