PARKE wrote on Yesterday, 09:14:

Do mobile chips with the same CPUID come with the same nomenclature ?

Often, but it would be wise to check what CPU World and/or Wikipedia says.

I added all the P4 Celerons and noted:

1. Celeron socket 478 + CPUID 0F1n should have Willamette
2. Celeron socket 478 + CPUID 0F2n should have Northwood
3. Celeron D 90-nm should have Prescott
4. Celeron D 300 should have Cedar Mill
5. Why do some have issue double and others just double?

In my opinion some are accidentally entered two times by the people who typed the data or one of the two identical S-Specs is incorrect and some may actually have been produced with identical S-Specs - like for example the PII SECC you are discussing. The jury is still out for that one imo.

PARKE wrote on Yesterday, 13:34:

The jury is still out for that one imo.

OK, I have been adding P4 Mobile.

1. Mobile P4 90-nm should have Prescott
2. Mobile Pentium 4-M should have Northwood
3. Mobile P4 533MHz fsb should have Northwood
4. Why are Mobile Pentium 4-M and Mobile P4 533MHz fsb very different when it's much the same CPU?

Thanks for all the additional names. The Mobile P4 90-nm from pdf 302441 is later and supports hyper-threading.

PARKE wrote on Yesterday, 15:26:

The Mobile P4 90-nm from pdf 302441 is later and supports hyper-threading.

OK, however I was really asking, why do the two Northwoods have very different names? Looking further one is Mobile P4 533MHz fsb

Also I noted below, given the 400MHz FSB then 2.33 GHz is impossible and https://www.cpu-world.com/sspec/SL/SL789.html says 2.30 GHz.

SL789 checked D1 0F29h 2.33GHz/400MHz Mobile Pentium 4-M 512KB sep 2002 35 1.3 400 2333.00 23 RK80532GC052512SL789 Malay

I have added more and noted:

1. Mobile Celeron 18u should have Coppermine
2. Mobile Celeron 13u + CPUID 068n should have Coppermine
3. Mobile Celeron 13u + CPUID 0x6Bn should have Tualatin

red-ray wrote on Yesterday, 18:39:

OK, however I was really asking, why do the two Northwoods have very different names? Looking further one is Mobile P4 533MHz fsb

Also I noted below, given the 400MHz FSB then 2.33 GHz is impossible

Yes, I sensed that you were asking that. The plan was to first import data from the available Intel sheets and weed trough the crop in the later phase. These headers derive from the sheets and I made them just to be able to sort the different categories and relate to the original specsheets - using just numbers doesn't work for me. Two weeks ago I had no idea that all those Intel cpu's had their own name. I have now changed all the P4's into Pentium 4

The 2.33GHZ is my fault, happened during individual/manual import.

Do you have the CPUID for Xeon L3406 ?

PARKE wrote on Today, 10:24:

Do you have the CPUID for Xeon L3406 ?

https://www.cpu-world.com/CPUs/Xeon/Int ... 3406).html says 20652, it's also says it's Clarkdale, SIV has:

SLBRX 020652 Clarkdale
SLBQQ 020652 Clarkdale
SLBT9 020655 Clarkdale
SLBT8 020655 Clarkdale

In general once you know the codename and stepping you can lookup the Signature/CPUID in the [ Windows CPU µCode Updates ] (Menu->Hardware->BIOS Tables->Windows CPU µCode) panel.

As far as I can tell SL9WN is CPUID 010661, https://www.cpu-world.com/sspec/SL/SL9WN.html does not list a CPUID, but https://www.cpu-world.com/sspec/SL/SLA2G.html lists 010661, I just found a SIV save from an Intel Celeron M 520 (Merom) CPUID 010661 and looking at https://en.wikipedia.org/wiki/List_of_I ... ge,_65_nm) there are only two possible and SL9WT is CPUID 0006F6.

This is the one with 10011b in the s-spec update.