lkml.org 
[lkml]   [2009]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [X86] Fix up silly i1586 boot message.
Date

<alpine.LSU.2.00.0910280914590.28170@obet.zrqbmnf.qr>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


> On Wednesday 2009-10-28 04:08=2C Yuhong Bao wrote:
>>=20
>>
>>> Intel started it first with picking up a ridiculous number for the fami=
ly
>>> ID for the P4 line. There is no technical justification for not keeping
>>> these numbers consecutive.
>
> Once one knows that there are 4 bits for the family field=2C 15 is not
> such a strange value - it is the last value=2C one could take it as
> "reserved=2C and look elsewhere".
Indeed=2C as I said=2C AMD began to use the extended family field with the =
K10.
>>[...] Intel has assigned family 7 for the original Itanium processor
>>[...] there was a bug in original NT 4 truncating family IDs
>>returned by CPUID [...]
>
> That would explain why Intel still shows an oldfashioned family=3D6 on
> many contemporary processors (e.g. core i7). BUT=2C AMD64 processors
> have family=3D15 "almost throughout"=2C and so seem to have at least some
> Intel models.=A0See my second mailing post message for why.
> So that tells us that either NT4 works=2C or nobody uses
> NT4 on fam15s.Family 15 truncated to 3 bits is family 7=2C which do work =
with NT 4=2C while family 8 truncated to 3 bits is family 0.
Yuhong bao =20
_________________________________________________________________
Windows 7: Simplify your PC. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=3DPID24727::T:=
WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen1:102009=


\
 
 \ /
  Last update: 2009-10-28 15:49    [W:0.063 / U:0.732 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site