Template talk:Intel processors

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Oni_Lukos-2005-07-26T19:51:00.000Z","type":"heading","level":0,"id":"h-Centrino-2005-07-26T19:51:00.000Z","replies":["c-Oni_Lukos-2005-07-26T19:51:00.000Z-Centrino"],"text":"Centrino","linkableTitle":"Centrino"}-->

Centrino

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Oni_Lukos-2005-07-26T19:51:00.000Z","type":"heading","level":0,"id":"h-Centrino-2005-07-26T19:51:00.000Z","replies":["c-Oni_Lukos-2005-07-26T19:51:00.000Z-Centrino"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Oni_Lukos-2005-07-26T19:51:00.000Z","type":"heading","level":0,"id":"h-Centrino-2005-07-26T19:51:00.000Z","replies":["c-Oni_Lukos-2005-07-26T19:51:00.000Z-Centrino"],"text":"Centrino","linkableTitle":"Centrino"}-->

I was looking through the processor list, and I noticed the distinct lack of Centrino. I would have added it, but I thought there might be a reason it was absent, like it being a subset of Pentium M (I don't know if that's true, but it could explain it). Anyone care to shed some light on this? ~ Oni Lukos (No, that's not my real name) c 19:51, 26 July 2005 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2005-07-26T19:51:00.000Z","author":"Oni Lukos","type":"comment","level":1,"id":"c-Oni_Lukos-2005-07-26T19:51:00.000Z-Centrino","replies":["c-Oni_Lukos-2005-08-10T18:03:00.000Z-Oni_Lukos-2005-07-26T19:51:00.000Z"]}}-->

Well, don't I feel stupid? I always assumed that Centrino was the actual processor line and not a combination of various things as the Centrino sticker on my laptop is in the same place as where there's usually a sticker denoting the processor used. I guess I should have read the article I linked to. ~ Oni Lukos c 18:03, 10 August 2005 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2005-08-10T18:03:00.000Z","author":"Oni Lukos","type":"comment","level":2,"id":"c-Oni_Lukos-2005-08-10T18:03:00.000Z-Oni_Lukos-2005-07-26T19:51:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Arch_dude-2007-05-09T03:45:00.000Z","type":"heading","level":0,"id":"h-Thanks!-2007-05-09T03:45:00.000Z","replies":["c-Arch_dude-2007-05-09T03:45:00.000Z-Thanks!"],"text":"Thanks!","linkableTitle":"Thanks!"}-->

Thanks!

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Arch_dude-2007-05-09T03:45:00.000Z","type":"heading","level":0,"id":"h-Thanks!-2007-05-09T03:45:00.000Z","replies":["c-Arch_dude-2007-05-09T03:45:00.000Z-Thanks!"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Arch_dude-2007-05-09T03:45:00.000Z","type":"heading","level":0,"id":"h-Thanks!-2007-05-09T03:45:00.000Z","replies":["c-Arch_dude-2007-05-09T03:45:00.000Z-Thanks!"],"text":"Thanks!","linkableTitle":"Thanks!"}-->

The split of "discontinued/continued" is a massive iprovement. I just split teh Itanium processors back to acommodate the split. -Arch dude 03:45, 9 May 2007 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2007-05-09T03:45:00.000Z","author":"Arch dude","type":"comment","level":1,"id":"c-Arch_dude-2007-05-09T03:45:00.000Z-Thanks!","replies":["c-Plugwash-2007-10-15T14:56:00.000Z-Arch_dude-2007-05-09T03:45:00.000Z"]}}-->

I'm not sure the split is correct though, it certainly contradicts the pentium 4 article which says the last shipment of pentium 4 processors will be in 2008. Plugwash 14:56, 15 October 2007 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2007-10-15T14:56:00.000Z","author":"Plugwash","type":"comment","level":2,"id":"c-Plugwash-2007-10-15T14:56:00.000Z-Arch_dude-2007-05-09T03:45:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-NapoliRoma-2007-06-01T21:26:00.000Z","type":"heading","level":0,"id":"h-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing-2007-06-01T21:26:00.000Z","replies":["c-NapoliRoma-2007-06-01T21:26:00.000Z-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing"],"text":"\"Intel CPU slots and sockets\" a bit confusing","linkableTitle":"\"Intel CPU slots and sockets\" a bit confusing"}-->

"Intel CPU slots and sockets" a bit confusing

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-NapoliRoma-2007-06-01T21:26:00.000Z","type":"heading","level":0,"id":"h-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing-2007-06-01T21:26:00.000Z","replies":["c-NapoliRoma-2007-06-01T21:26:00.000Z-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-NapoliRoma-2007-06-01T21:26:00.000Z","type":"heading","level":0,"id":"h-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing-2007-06-01T21:26:00.000Z","replies":["c-NapoliRoma-2007-06-01T21:26:00.000Z-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing"],"text":"\"Intel CPU slots and sockets\" a bit confusing","linkableTitle":"\"Intel CPU slots and sockets\" a bit confusing"}-->

It could be just me, but I find the current layout to be a little confusing. The current rows look like this:

Box 1 (color 1):     Intel _processors_
  Box 2 (color 2):         Discontinued | (list)
  Box 3 (color 2):              Current | (list)
Box 4 (color 1):     _Intel CPU slots and sockets_
                      Italics indicate non-x86 processors.

What this said to me when I read it is that line 1 was a header for a table. Lines 2 and 3 were clearly payload for that header, being in a different color, and having individual row labels, each having lots of clickable content. OK so far.

So what's line 4? It looks like a header -- same color as line 1, centered text, bold. So where's the payload? Given its resemblance to a header, I expected to see a list of slots/sockets. Since (most of) the "real" header is clickable, but still has a table of links to follow, it wasn't obvious to me that the real content for maybe-header is only to be found by clicking on it.

Also in this maybe-header is a comment about what italics mean, but there are no italics in this box. This little bit of explanation is separated from the thing it's really explaining.

I would suggest changing this to look something like:

Box 1 (color 1): Intel _processors_ (Italics indicate non-x86 processors) Box 2 (color 2): Discontinued | (list) Box 3 (color 2): Current | (list) Box 4 (color 2): Slots / Sockets | See _CPU socket_ --NapoliRoma 21:26, 1 June 2007 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2007-06-01T21:26:00.000Z","author":"NapoliRoma","type":"comment","level":1,"id":"c-NapoliRoma-2007-06-01T21:26:00.000Z-\"Intel_CPU_slots_and_sockets\"_a_bit_confusing","replies":[]}}-->

Rather than a text representation, here's a coded example of what I think would be a less confusing layout:

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Rada-2007-10-19T06:55:00.000Z","type":"heading","level":0,"id":"h-Discontinued_vs_Current_Processors-2007-10-19T06:55:00.000Z","replies":["c-Rada-2007-10-19T06:55:00.000Z-Discontinued_vs_Current_Processors","c-Jdlowery-2008-01-16T01:30:00.000Z-Discontinued_vs_Current_Processors","c-Ramu50-2008-07-28T22:09:00.000Z-Discontinued_vs_Current_Processors"],"text":"Discontinued vs Current Processors","linkableTitle":"Discontinued vs Current Processors"}-->

Discontinued vs Current Processors

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Rada-2007-10-19T06:55:00.000Z","type":"heading","level":0,"id":"h-Discontinued_vs_Current_Processors-2007-10-19T06:55:00.000Z","replies":["c-Rada-2007-10-19T06:55:00.000Z-Discontinued_vs_Current_Processors","c-Jdlowery-2008-01-16T01:30:00.000Z-Discontinued_vs_Current_Processors","c-Ramu50-2008-07-28T22:09:00.000Z-Discontinued_vs_Current_Processors"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Rada-2007-10-19T06:55:00.000Z","type":"heading","level":0,"id":"h-Discontinued_vs_Current_Processors-2007-10-19T06:55:00.000Z","replies":["c-Rada-2007-10-19T06:55:00.000Z-Discontinued_vs_Current_Processors","c-Jdlowery-2008-01-16T01:30:00.000Z-Discontinued_vs_Current_Processors","c-Ramu50-2008-07-28T22:09:00.000Z-Discontinued_vs_Current_Processors"],"text":"Discontinued vs Current Processors","linkableTitle":"Discontinued vs Current Processors"}-->

I'm sorry but whomever took it upon themselves to label many still in production processors as discontinued really should have seen which had been discontinued. http://www.intel.com/products/embedded/processors.htm?iid=process+embed shows the processors in current production. Really the only discontinued CPU's are <=i486 and the <=i960 and the 386 and 486 only gained this status in summer 2006 (http://www.embedded.com/columns/embeddedpulse/188500905?_requestid=277155). At the very least, a clarification is needed as to which are 'current' and 'discontinued' since there is only a small fraction of those parts now actually discontinued.

Rada 06:55, 19 October 2007 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2007-10-19T06:55:00.000Z","author":"Rada","type":"comment","level":1,"id":"c-Rada-2007-10-19T06:55:00.000Z-Discontinued_vs_Current_Processors","replies":[]}}-->

The link you provided shows embedded products. What that means is that these are no longer current products and are in an extended life cycle phase for embedded applications only! Further more, I am a computer tech and I know that these are discontinued products. Intel discontinued the Pentium M in favor of the newer 65nm Pentium Dual core and Celeron M processors. Production for the 90nm CPUs ended at the end of 2007. We no longer can get Pentium M processors in our store for custom laptop builds. They are in an embedded life cycle phase! The only Pentium D processors currently being manufactured are the 925 and 945 models and that too will end in the second half of 2008. That means that these are no longer mainstream products, hence the term discontinued. Jdlowery (talk) 01:30, 16 January 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-01-16T01:30:00.000Z","author":"Jdlowery","type":"comment","level":1,"id":"c-Jdlowery-2008-01-16T01:30:00.000Z-Discontinued_vs_Current_Processors","replies":[]}}-->

Intel Pentium M is not a discontinued product, MID platform still uses them as see in here. --Ramu50 (talk) 22:09, 28 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-28T22:09:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-07-28T22:09:00.000Z-Discontinued_vs_Current_Processors","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-189.31.94.176-2008-05-26T23:55:00.000Z","type":"heading","level":0,"id":"h-Nehalem_and_Sandy_Bridge-2008-05-26T23:55:00.000Z","replies":["c-189.31.94.176-2008-05-26T23:55:00.000Z-Nehalem_and_Sandy_Bridge","c-Ramu50-2008-08-16T19:32:00.000Z-Nehalem_and_Sandy_Bridge"],"text":"Nehalem and Sandy Bridge","linkableTitle":"Nehalem and Sandy Bridge"}-->

Nehalem and Sandy Bridge

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-189.31.94.176-2008-05-26T23:55:00.000Z","type":"heading","level":0,"id":"h-Nehalem_and_Sandy_Bridge-2008-05-26T23:55:00.000Z","replies":["c-189.31.94.176-2008-05-26T23:55:00.000Z-Nehalem_and_Sandy_Bridge","c-Ramu50-2008-08-16T19:32:00.000Z-Nehalem_and_Sandy_Bridge"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-189.31.94.176-2008-05-26T23:55:00.000Z","type":"heading","level":0,"id":"h-Nehalem_and_Sandy_Bridge-2008-05-26T23:55:00.000Z","replies":["c-189.31.94.176-2008-05-26T23:55:00.000Z-Nehalem_and_Sandy_Bridge","c-Ramu50-2008-08-16T19:32:00.000Z-Nehalem_and_Sandy_Bridge"],"text":"Nehalem and Sandy Bridge","linkableTitle":"Nehalem and Sandy Bridge"}-->

Shouldn't we put the Nehalem and the Sandy Bridge into the speculated list of the template? 189.31.94.176 (talk) 23:55, 26 May 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-05-26T23:55:00.000Z","author":"189.31.94.176","type":"comment","level":1,"id":"c-189.31.94.176-2008-05-26T23:55:00.000Z-Nehalem_and_Sandy_Bridge","replies":["c-Makelelecba-2008-06-03T18:56:00.000Z-189.31.94.176-2008-05-26T23:55:00.000Z"]}}-->

-- Agree, and done. Cheers! --MakE shout! 18:56, 3 June 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-06-03T18:56:00.000Z","author":"Makelelecba","type":"comment","level":2,"id":"c-Makelelecba-2008-06-03T18:56:00.000Z-189.31.94.176-2008-05-26T23:55:00.000Z","replies":[],"displayName":"MakE"}}-->

Totally disagree. Architecture generally refers to the architecture of a processor, however, it most cases it also include the architecture of the chipset itself, the interconnect of implantation of a chipset generally will affect some minor changes of server processor so I suggest don't fuse them to prevention confusion. --Ramu50 (talk) 19:32, 16 August 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-08-16T19:32:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-08-16T19:32:00.000Z-Nehalem_and_Sandy_Bridge","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Ramu50-2008-07-15T18:10:00.000Z","type":"heading","level":0,"id":"h-Request_information_to_be_added-2008-07-15T18:10:00.000Z","replies":["c-Ramu50-2008-07-15T18:10:00.000Z-Request_information_to_be_added","c-Ramu50-2008-07-18T19:15:00.000Z-Request_information_to_be_added"],"text":"Request information to be added","linkableTitle":"Request information to be added"}-->

Request information to be added

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Ramu50-2008-07-15T18:10:00.000Z","type":"heading","level":0,"id":"h-Request_information_to_be_added-2008-07-15T18:10:00.000Z","replies":["c-Ramu50-2008-07-15T18:10:00.000Z-Request_information_to_be_added","c-Ramu50-2008-07-18T19:15:00.000Z-Request_information_to_be_added"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Ramu50-2008-07-15T18:10:00.000Z","type":"heading","level":0,"id":"h-Request_information_to_be_added-2008-07-15T18:10:00.000Z","replies":["c-Ramu50-2008-07-15T18:10:00.000Z-Request_information_to_be_added","c-Ramu50-2008-07-18T19:15:00.000Z-Request_information_to_be_added"],"text":"Request information to be added","linkableTitle":"Request information to be added"}-->

Can somebody add the following

Network Processor IPX2XXX(SONET & ATM), IP4XX(LAN/WAN integrated & embedded), IP12XX (SONET) ref.


I/O Processor (the RAID controller on chipset)

  • I/O SoC
    • IOP322

Link it via Network processor, I think it is the best article we got so far --Ramu50 (talk) 18:10, 15 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-15T18:10:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-07-15T18:10:00.000Z-Request_information_to_be_added","replies":[]}}-->
Info Updated: --Ramu50 (talk) 19:15, 18 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-18T19:15:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-07-18T19:15:00.000Z-Request_information_to_be_added","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Jdlowery-2008-07-16T19:13:00.000Z","type":"heading","level":0,"id":"h-Netburst_processor_discontinuance-2008-07-16T19:13:00.000Z","replies":["c-Jdlowery-2008-07-16T19:13:00.000Z-Netburst_processor_discontinuance"],"text":"Netburst processor discontinuance","linkableTitle":"Netburst processor discontinuance"}-->

Netburst processor discontinuance

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Jdlowery-2008-07-16T19:13:00.000Z","type":"heading","level":0,"id":"h-Netburst_processor_discontinuance-2008-07-16T19:13:00.000Z","replies":["c-Jdlowery-2008-07-16T19:13:00.000Z-Netburst_processor_discontinuance"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Jdlowery-2008-07-16T19:13:00.000Z","type":"heading","level":0,"id":"h-Netburst_processor_discontinuance-2008-07-16T19:13:00.000Z","replies":["c-Jdlowery-2008-07-16T19:13:00.000Z-Netburst_processor_discontinuance"],"text":"Netburst processor discontinuance","linkableTitle":"Netburst processor discontinuance"}-->

For those of you who think that the Netburst based processors Pentium 4, Pentium D, and Pentium Extreme are still current, think again. Intel has moved on from these products and has already replaced them with the Core 2 Duo line. These Netburst based processors have already entered Intel's product discontinuance program and are being phased out completely. Last shipments on all retail (boxed) Netburst based processors were made March 7, 2008 and OEM (tray) processors will be made on August 8, 2008. After this date, these products will be completely gone. This means Intel no longer produces these products. This also means that these countries who are still selling these products are just selling existing stock. This could continue for years down the road, but the key here when we say they are discontinued products is that Intel no longer actually produces them. Please read this article for further details on the matter.Jdlowery (talk) 19:13, 16 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-16T19:13:00.000Z","author":"Jdlowery","type":"comment","level":1,"id":"c-Jdlowery-2008-07-16T19:13:00.000Z-Netburst_processor_discontinuance","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Ramu50-2008-07-18T19:23:00.000Z","type":"heading","level":0,"id":"h-Template_Overall_Organization-2008-07-18T19:23:00.000Z","replies":["c-Ramu50-2008-07-18T19:23:00.000Z-Template_Overall_Organization","c-Ramu50-2008-07-20T23:54:00.000Z-Template_Overall_Organization"],"text":"Template Overall Organization","linkableTitle":"Template Overall Organization"}-->

Template Overall Organization

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Ramu50-2008-07-18T19:23:00.000Z","type":"heading","level":0,"id":"h-Template_Overall_Organization-2008-07-18T19:23:00.000Z","replies":["c-Ramu50-2008-07-18T19:23:00.000Z-Template_Overall_Organization","c-Ramu50-2008-07-20T23:54:00.000Z-Template_Overall_Organization"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Ramu50-2008-07-18T19:23:00.000Z","type":"heading","level":0,"id":"h-Template_Overall_Organization-2008-07-18T19:23:00.000Z","replies":["c-Ramu50-2008-07-18T19:23:00.000Z-Template_Overall_Organization","c-Ramu50-2008-07-20T23:54:00.000Z-Template_Overall_Organization"],"text":"Template Overall Organization","linkableTitle":"Template Overall Organization"}-->

I propose we do the following

  • Discontinued
  • Current (Desktop)
  • Current (Mobile)
  • List (common)
    • Processors
    • Codenames
    • Chipsets

List (enterprise, workstation or servers)

  • Slots and Sockets

I think it will be a lot more organized. I don't think we need List of Atom, Celeron, Core, Core 2, Itanium, Itanium II, Pentium II, Pentium III, Pentium 4, Pentium D, Pentium Dual Core, Pentium M and Xeon. Most people don't even use these links at all. --Ramu50 (talk) 19:23, 18 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-18T19:23:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-07-18T19:23:00.000Z-Template_Overall_Organization","replies":["c-Jeh-2008-07-19T18:12:00.000Z-Ramu50-2008-07-18T19:23:00.000Z"]}}-->

"most people don't even use these links"? I don't see how one editor can have such information. I see no reason to exclude such names from the template. Jeh (talk) 18:12, 19 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-19T18:12:00.000Z","author":"Jeh","type":"comment","level":2,"id":"c-Jeh-2008-07-19T18:12:00.000Z-Ramu50-2008-07-18T19:23:00.000Z","replies":[]}}-->

Actually just make a section called other and have a link called Index, list of... or make it a stub of the template, because some list include discontinued and current which is conflicting. --Ramu50 (talk) 23:54, 20 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-20T23:54:00.000Z","author":"Ramu50","type":"comment","level":1,"id":"c-Ramu50-2008-07-20T23:54:00.000Z-Template_Overall_Organization","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Jeh-2008-07-19T18:12:00.000Z","type":"heading","level":0,"id":"h-Codenames:_not_just_for_futures-2008-07-19T18:12:00.000Z","replies":["c-Jeh-2008-07-19T18:12:00.000Z-Codenames:_not_just_for_futures"],"text":"Codenames: not just for futures","linkableTitle":"Codenames: not just for futures"}-->

Codenames: not just for futures

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Jeh-2008-07-19T18:12:00.000Z","type":"heading","level":0,"id":"h-Codenames:_not_just_for_futures-2008-07-19T18:12:00.000Z","replies":["c-Jeh-2008-07-19T18:12:00.000Z-Codenames:_not_just_for_futures"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Jeh-2008-07-19T18:12:00.000Z","type":"heading","level":0,"id":"h-Codenames:_not_just_for_futures-2008-07-19T18:12:00.000Z","replies":["c-Jeh-2008-07-19T18:12:00.000Z-Codenames:_not_just_for_futures"],"text":"Codenames: not just for futures","linkableTitle":"Codenames: not just for futures"}-->

I don't think the list of codenames should be restricted to future products. It should include already-released names such as "Dothan", "Merom", "Penryn", "Coppermine", etc., linking to the articles describing those products or technologies. Just because a code name no longer is a "future" doesn't mean people won't be wondering about what it means. It's true that the regular WP search will find these things, but that can be much more circuituous. Links in a template are cheap. And being from the past, they'll be very easy to maintain. :) Jeh (talk) 18:12, 19 July 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-07-19T18:12:00.000Z","author":"Jeh","type":"comment","level":1,"id":"c-Jeh-2008-07-19T18:12:00.000Z-Codenames:_not_just_for_futures","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Althepal-2008-08-17T20:20:00.000Z","type":"heading","level":0,"id":"h-Lists_of_\"speculated\"-2008-08-17T20:20:00.000Z","replies":["c-Althepal-2008-08-17T20:20:00.000Z-Lists_of_\"speculated\""],"text":"Lists of \"speculated\"","linkableTitle":"Lists of \"speculated\""}-->

Lists of "speculated"

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Althepal-2008-08-17T20:20:00.000Z","type":"heading","level":0,"id":"h-Lists_of_\"speculated\"-2008-08-17T20:20:00.000Z","replies":["c-Althepal-2008-08-17T20:20:00.000Z-Lists_of_\"speculated\""]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Althepal-2008-08-17T20:20:00.000Z","type":"heading","level":0,"id":"h-Lists_of_\"speculated\"-2008-08-17T20:20:00.000Z","replies":["c-Althepal-2008-08-17T20:20:00.000Z-Lists_of_\"speculated\""],"text":"Lists of \"speculated\"","linkableTitle":"Lists of \"speculated\""}-->

Shouldn't the "Lists of speculated" part of the template be renamed "Future" or something? I mean Wikipedia isn't a rumors site for one thing. And even if "speculated" stays, the extra "Lists of" words don't seem to be needed. Althepal (talk) 20:20, 17 August 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-08-17T20:20:00.000Z","author":"Althepal","type":"comment","level":1,"id":"c-Althepal-2008-08-17T20:20:00.000Z-Lists_of_\"speculated\"","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-200.148.45.132-2008-08-25T13:00:00.000Z","type":"heading","level":0,"id":"h-A100-2008-08-25T13:00:00.000Z","replies":["c-200.148.45.132-2008-08-25T13:00:00.000Z-A100"],"text":"A100","linkableTitle":"A100"}-->

A100

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-200.148.45.132-2008-08-25T13:00:00.000Z","type":"heading","level":0,"id":"h-A100-2008-08-25T13:00:00.000Z","replies":["c-200.148.45.132-2008-08-25T13:00:00.000Z-A100"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-200.148.45.132-2008-08-25T13:00:00.000Z","type":"heading","level":0,"id":"h-A100-2008-08-25T13:00:00.000Z","replies":["c-200.148.45.132-2008-08-25T13:00:00.000Z-A100"],"text":"A100","linkableTitle":"A100"}-->

The A100 series is not ARM based, it's x86 (as it's article also points).--200.148.45.132 (talk) 13:00, 25 August 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-08-25T13:00:00.000Z","author":"200.148.45.132","type":"comment","level":1,"id":"c-200.148.45.132-2008-08-25T13:00:00.000Z-A100","replies":["c-Burnte-2008-08-26T03:18:00.000Z-200.148.45.132-2008-08-25T13:00:00.000Z"]}}-->

Fixed! Thanks! burnte (talk) 03:18, 26 August 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-08-26T03:18:00.000Z","author":"Burnte","type":"comment","level":2,"id":"c-Burnte-2008-08-26T03:18:00.000Z-200.148.45.132-2008-08-25T13:00:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Burnte-2008-09-01T23:13:00.000Z","type":"heading","level":0,"id":"h-Consolidation-2008-09-01T23:13:00.000Z","replies":["c-Burnte-2008-09-01T23:13:00.000Z-Consolidation"],"text":"Consolidation","linkableTitle":"Consolidation"}-->

Consolidation

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Burnte-2008-09-01T23:13:00.000Z","type":"heading","level":0,"id":"h-Consolidation-2008-09-01T23:13:00.000Z","replies":["c-Burnte-2008-09-01T23:13:00.000Z-Consolidation"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Burnte-2008-09-01T23:13:00.000Z","type":"heading","level":0,"id":"h-Consolidation-2008-09-01T23:13:00.000Z","replies":["c-Burnte-2008-09-01T23:13:00.000Z-Consolidation"],"text":"Consolidation","linkableTitle":"Consolidation"}-->
  1. I've consolidated the two different lists of lists, because it's stupid to have two different list lines.
  2. I've consolidated the only non-duplicate link on the MID line to where it should be. All the other items in teh MID line are duplicate or not linked. #Also, that's a type of system, not a type of processor. it's not fit for this template.
  3. I've consolidated the non x86 processors into one line for multiple reasons. We don't need to double the size od teh Discontinued list for a handful of minor chips. Also, we don't need one or two items on a line, and have several of those lines. Also, Itanium isn't called VLIW by Intel. VLIW is a type of design that Itanium happens to fall under, like RISC or CISC. Itanium is IA-64 and now IIA, Intel Itanium Archetechture, NOT VLIW. Stop reverting it to VLIW, it's inaccurate.
  4. This template needs to be concise, easy to use, and not littered with poorly structured lists. It should convey the needed information simply, not be a tree-of-life rivaling a taxonomic reference.

If you disagree, let's discuss the direction rather than just making plain bad edits to the template. burnte (talk) 23:13, 1 September 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-09-01T23:13:00.000Z","author":"Burnte","type":"comment","level":1,"id":"c-Burnte-2008-09-01T23:13:00.000Z-Consolidation","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Rilak-2008-10-29T12:58:00.000Z","type":"heading","level":0,"id":"h-Restore_to_original_version?-2008-10-29T12:58:00.000Z","replies":["c-Rilak-2008-10-29T12:58:00.000Z-Restore_to_original_version?"],"text":"Restore to original version?","linkableTitle":"Restore to original version?"}-->

Restore to original version?

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Rilak-2008-10-29T12:58:00.000Z","type":"heading","level":0,"id":"h-Restore_to_original_version?-2008-10-29T12:58:00.000Z","replies":["c-Rilak-2008-10-29T12:58:00.000Z-Restore_to_original_version?"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Rilak-2008-10-29T12:58:00.000Z","type":"heading","level":0,"id":"h-Restore_to_original_version?-2008-10-29T12:58:00.000Z","replies":["c-Rilak-2008-10-29T12:58:00.000Z-Restore_to_original_version?"],"text":"Restore to original version?","linkableTitle":"Restore to original version?"}-->

Would restoring the navbox to the simple and usable version be a good idea? Rilak (talk) 12:58, 29 October 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-10-29T12:58:00.000Z","author":"Rilak","type":"comment","level":1,"id":"c-Rilak-2008-10-29T12:58:00.000Z-Restore_to_original_version?","replies":["c-Rilak-2008-12-03T07:39:00.000Z-Rilak-2008-10-29T12:58:00.000Z"]}}-->

Since there was no consensus for restoring the navbox to a more simple revision, I have removed links not in the scope of Intel processors. Of note are:
  • The links to articles about Intel microcontrollers, there is already a better template for those: Template:Intel controllers
  • The links to platforms - it is rather obvious that they are not processors when the lead sentence of such articles go something like this, "xyz is not a processor, but a collection of xyz/an initiative..."
Rilak (talk) 07:39, 3 December 2008 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2008-12-03T07:39:00.000Z","author":"Rilak","type":"comment","level":2,"id":"c-Rilak-2008-12-03T07:39:00.000Z-Rilak-2008-10-29T12:58:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Arndbergmann-2009-08-20T13:43:00.000Z","type":"heading","level":0,"id":"h-list_of_cores-2009-08-20T13:43:00.000Z","replies":["c-Arndbergmann-2009-08-20T13:43:00.000Z-list_of_cores"],"text":"list of cores","linkableTitle":"list of cores"}-->

list of cores

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Arndbergmann-2009-08-20T13:43:00.000Z","type":"heading","level":0,"id":"h-list_of_cores-2009-08-20T13:43:00.000Z","replies":["c-Arndbergmann-2009-08-20T13:43:00.000Z-list_of_cores"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Arndbergmann-2009-08-20T13:43:00.000Z","type":"heading","level":0,"id":"h-list_of_cores-2009-08-20T13:43:00.000Z","replies":["c-Arndbergmann-2009-08-20T13:43:00.000Z-list_of_cores"],"text":"list of cores","linkableTitle":"list of cores"}-->

I've added a list of all the cores in x86 processors since P5, sorted by microarchitecture and fabrication process, as part of the way out of Intel's naming nightmare. I'm not entirely happy with the new layout, but it's the best I could come up with. Maybe someone can still improve it.

For new processor core that are used in different brand names (e.g. Lynnfield in Core i5 and Core i7), the conclusion was to describe the specific features of the core in one article and link to that one from the article describing the brands. The same could be done for existing cores, e.g. Allendale, which is used in four different brands (Celeron, Pentium, Core 2 and Xeon). Arndbergmann (talk) 13:43, 20 August 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-08-20T13:43:00.000Z","author":"Arndbergmann","type":"comment","level":1,"id":"c-Arndbergmann-2009-08-20T13:43:00.000Z-list_of_cores","replies":["c-Fernvale-2009-08-27T14:23:00.000Z-Arndbergmann-2009-08-20T13:43:00.000Z"]}}-->

  • Restore back to original version, all codenames can be found in list of each intel processors. Fernvale (talk) 14:23, 27 August 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-08-27T14:23:00.000Z","author":"Fernvale","type":"comment","level":2,"id":"c-Fernvale-2009-08-27T14:23:00.000Z-Arndbergmann-2009-08-20T13:43:00.000Z","replies":["c-Arndbergmann-2009-08-27T21:14:00.000Z-Fernvale-2009-08-27T14:23:00.000Z"]}}-->
    That works for the old P5, P6 and Netburst microarchitectures, but not for Core and Nehalem. There, the code names are really what differentiates processors, while the brand names are mostly meaningless and most cores are used in two or three brands (core 2, pentium, core i3, core i5, core i7, ...). If we get one article per core, IMHO there should be a way to navigate between them other than cross-referencing from some random brand page.
    How about splitting the Cores section of the 'Template:Intel processors' into a different Navbox that only gets included for articles describing any of the cores? Arndbergmann (talk) 21:14, 27 August 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-08-27T21:14:00.000Z","author":"Arndbergmann","type":"comment","level":3,"id":"c-Arndbergmann-2009-08-27T21:14:00.000Z-Fernvale-2009-08-27T14:23:00.000Z","replies":["c-Vossanova-2009-09-04T17:38:00.000Z-Arndbergmann-2009-08-27T21:14:00.000Z"]}}-->
    I like that idea. Adding cores into the template for all Intel CPU articles is a little overkill. Either link to a list of intel cores in the template or make a separate core template. --Vossanova o< 17:38, 4 September 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-09-04T17:38:00.000Z","author":"Vossanova","type":"comment","level":4,"id":"c-Vossanova-2009-09-04T17:38:00.000Z-Arndbergmann-2009-08-27T21:14:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-AnonMoos-2009-11-15T23:57:00.000Z","type":"heading","level":0,"id":"h-87_missing?-2009-11-15T23:57:00.000Z","replies":["c-AnonMoos-2009-11-15T23:57:00.000Z-87_missing?"],"text":"87 missing?","linkableTitle":"87 missing?"}-->

87 missing?

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-AnonMoos-2009-11-15T23:57:00.000Z","type":"heading","level":0,"id":"h-87_missing?-2009-11-15T23:57:00.000Z","replies":["c-AnonMoos-2009-11-15T23:57:00.000Z-87_missing?"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-AnonMoos-2009-11-15T23:57:00.000Z","type":"heading","level":0,"id":"h-87_missing?-2009-11-15T23:57:00.000Z","replies":["c-AnonMoos-2009-11-15T23:57:00.000Z-87_missing?"],"text":"87 missing?","linkableTitle":"87 missing?"}-->

The template should include some kind of link to Intel 8087 and/or x87 -- that would seem to be a lot more important topic than the 80188... AnonMoos (talk) 23:57, 15 November 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-11-15T23:57:00.000Z","author":"AnonMoos","type":"comment","level":1,"id":"c-AnonMoos-2009-11-15T23:57:00.000Z-87_missing?","replies":["c-Alinor-2010-02-14T11:48:00.000Z-AnonMoos-2009-11-15T23:57:00.000Z"]}}-->

Done. Alinor (talk) 11:48, 14 February 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-02-14T11:48:00.000Z","author":"Alinor","type":"comment","level":2,"id":"c-Alinor-2010-02-14T11:48:00.000Z-AnonMoos-2009-11-15T23:57:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-LAPS-2010-07-19T01:30:00.000Z","type":"heading","level":0,"id":"h-State_-_autocollapse-2010-07-19T01:30:00.000Z","replies":["c-LAPS-2010-07-19T01:30:00.000Z-State_-_autocollapse"],"text":"State - autocollapse","linkableTitle":"State - autocollapse"}-->

State - autocollapse

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-LAPS-2010-07-19T01:30:00.000Z","type":"heading","level":0,"id":"h-State_-_autocollapse-2010-07-19T01:30:00.000Z","replies":["c-LAPS-2010-07-19T01:30:00.000Z-State_-_autocollapse"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-LAPS-2010-07-19T01:30:00.000Z","type":"heading","level":0,"id":"h-State_-_autocollapse-2010-07-19T01:30:00.000Z","replies":["c-LAPS-2010-07-19T01:30:00.000Z-State_-_autocollapse"],"text":"State - autocollapse","linkableTitle":"State - autocollapse"}-->

As it mentioned over on the AMD processors page, I believe that this navbox has also gotten quite large and that an autocollapse state setting should be discussed. Thanks! The Tech Geek (talk) 01:30, 19 July 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-07-19T01:30:00.000Z","author":"LAPS","type":"comment","level":1,"id":"c-LAPS-2010-07-19T01:30:00.000Z-State_-_autocollapse","replies":["c-173.50.233.227-2010-08-07T16:06:00.000Z-LAPS-2010-07-19T01:30:00.000Z"],"displayName":"The Tech Geek"}}-->

For reference, I believe this is the discussion: Template talk:AMD processors#State - autocollapse 173.50.233.227 (talk) 16:06, 7 August 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-08-07T16:06:00.000Z","author":"173.50.233.227","type":"comment","level":2,"id":"c-173.50.233.227-2010-08-07T16:06:00.000Z-LAPS-2010-07-19T01:30:00.000Z","replies":["c-Music_Sorter-2010-12-26T22:25:00.000Z-173.50.233.227-2010-08-07T16:06:00.000Z"]}}-->
Since we did it for the AMD template, I believe we need to do the same for the Intel template so I applied that autocollapse setting today. § Music Sorter § (talk) 22:25, 26 December 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-12-26T22:25:00.000Z","author":"Music Sorter","type":"comment","level":3,"id":"c-Music_Sorter-2010-12-26T22:25:00.000Z-173.50.233.227-2010-08-07T16:06:00.000Z","replies":["c-173.50.233.227-2011-01-10T13:49:00.000Z-Music_Sorter-2010-12-26T22:25:00.000Z"],"displayName":"\u00a7\u00a0Music\u00a0Sorter\u00a0\u00a7"}}-->
One issue with doing this is this navbox uses several collapsible sub-navboxes, unlike the AMD processors template, so setting "autocollapse" degrades to (always) "collapsed". 173.50.233.227 (talk) 13:49, 10 January 2011 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2011-01-10T13:49:00.000Z","author":"173.50.233.227","type":"comment","level":4,"id":"c-173.50.233.227-2011-01-10T13:49:00.000Z-Music_Sorter-2010-12-26T22:25:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Uzume-2011-01-15T01:32:00.000Z","type":"heading","level":0,"id":"h-Vermilion_Range-2011-01-15T01:32:00.000Z","replies":["c-Uzume-2011-01-15T01:32:00.000Z-Vermilion_Range"],"text":"Vermilion Range","linkableTitle":"Vermilion Range"}-->

Vermilion Range

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Uzume-2011-01-15T01:32:00.000Z","type":"heading","level":0,"id":"h-Vermilion_Range-2011-01-15T01:32:00.000Z","replies":["c-Uzume-2011-01-15T01:32:00.000Z-Vermilion_Range"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Uzume-2011-01-15T01:32:00.000Z","type":"heading","level":0,"id":"h-Vermilion_Range-2011-01-15T01:32:00.000Z","replies":["c-Uzume-2011-01-15T01:32:00.000Z-Vermilion_Range"],"text":"Vermilion Range","linkableTitle":"Vermilion Range"}-->

This seems to be the best place to discuss Intel processors lists (it being sort of a list of lists). My question is where does one put the following:

"Vermilion Range"

Model sSpec Frequency Product Code
EP80578
  • SLH4J
  • SLADH
  • SLAAC
800 MHz LE80578EG800C
EP80578
  • SLH6E
  • SLADJ
  • SLAAD
1.2 GHz LE80578EG009C
EP80578
  • SLH6F
  • SLAHW
1.0 GHz LE80578EG001C

Linkage information between model names, frequencies, and product codes based on PCN110389. sSpec numbers based on product codes indexed into qdms.intel.com. Uzume (talk) 01:32, 15 January 2011 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2011-01-15T01:32:00.000Z","author":"Uzume","type":"comment","level":1,"id":"c-Uzume-2011-01-15T01:32:00.000Z-Vermilion_Range","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Robertbyrne-2011-09-20T19:04:00.000Z","type":"heading","level":0,"id":"h-\"Intel_Core\"_ambiguity-2011-09-20T19:04:00.000Z","replies":["c-Robertbyrne-2011-09-20T19:04:00.000Z-\"Intel_Core\"_ambiguity"],"text":"\"Intel Core\" ambiguity","linkableTitle":"\"Intel Core\" ambiguity"}-->

"Intel Core" ambiguity

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Robertbyrne-2011-09-20T19:04:00.000Z","type":"heading","level":0,"id":"h-\"Intel_Core\"_ambiguity-2011-09-20T19:04:00.000Z","replies":["c-Robertbyrne-2011-09-20T19:04:00.000Z-\"Intel_Core\"_ambiguity"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Robertbyrne-2011-09-20T19:04:00.000Z","type":"heading","level":0,"id":"h-\"Intel_Core\"_ambiguity-2011-09-20T19:04:00.000Z","replies":["c-Robertbyrne-2011-09-20T19:04:00.000Z-\"Intel_Core\"_ambiguity"],"text":"\"Intel Core\" ambiguity","linkableTitle":"\"Intel Core\" ambiguity"}-->

The section "Discontinued", sub-section "IA-32" includes "Core" which links to Intel Core. The section "Current", sub-section "x86-64" also includes "Core" which also links to Intel Core. I can see that the Intel Core article covers both discontinued and current processor lines, but the navbox categorization makes the reader do extra work to resolve what the reference to "Core" actually means.

Proposal: Entries in the template should refer to a clear and distinct product line, and the link text should indicate something about what product line that is. For example (and I am *not* an expert on these CPU lines! This is an example purely to illustrate my point!) how about the discontinued, 32-bit processors are referred to as "Core x" while the current, 64-bit processors are referred to as "Core ix" or "Core x and Core ix".

I know there are difficulties distinguishing which processors are current and which are discontinued, and the naming schemes are not likely to cooperate with a clear distinction, but I suspect that this navbox could work a little harder at explaining what it is talking about. Either that, or perhaps the navbox should be simplified and not try to split the product lines up by whether they are current or even by whether they are 32-bit or 64-bit.

Do any subject experts agree with me? By the way, I realise that this affects some other entries such as "Pentium". An effort to distinguish what is meant by multiple "Pentium" entries would be useful too. Robertbyrne (talk) 19:04, 20 September 2011 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2011-09-20T19:04:00.000Z","author":"Robertbyrne","type":"comment","level":1,"id":"c-Robertbyrne-2011-09-20T19:04:00.000Z-\"Intel_Core\"_ambiguity","replies":["c-Arndbergmann-2011-09-21T07:48:00.000Z-Robertbyrne-2011-09-20T19:04:00.000Z"]}}-->

The problem of splitting the tables into 'Discontinued' and 'Current' is the same for all six current lines of processors (Atom, Celeron, Pentium, Core, Xeon and Itanium). The Pentium one is special here because it has the most complex history and there are separate articles for the distinct brand names (Pentium Pro/2/3/4/D/M/...) which are not there for the other ones. We could solve this by always linking to the specific products and not to the broader family name in the 'Discontinued' rows, like "Pentium (Original * Pro * II * III * ...) * Core (Solo * Duo)". There are also other inaccuracies, e.g. Pentium Dual-Core and Atom both have discontinued 32 and 64 bit models. Arndbergmann (talk) 07:48, 21 September 2011 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2011-09-21T07:48:00.000Z","author":"Arndbergmann","type":"comment","level":2,"id":"c-Arndbergmann-2011-09-21T07:48:00.000Z-Robertbyrne-2011-09-20T19:04:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-MrBurns-2013-06-12T18:22:00.000Z","type":"heading","level":0,"id":"h-Haswell\/Broadwell-2013-06-12T18:22:00.000Z","replies":["c-MrBurns-2013-06-12T18:22:00.000Z-Haswell\/Broadwell"],"text":"Haswell\/Broadwell","linkableTitle":"Haswell\/Broadwell"}-->

Haswell/Broadwell

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-MrBurns-2013-06-12T18:22:00.000Z","type":"heading","level":0,"id":"h-Haswell\/Broadwell-2013-06-12T18:22:00.000Z","replies":["c-MrBurns-2013-06-12T18:22:00.000Z-Haswell\/Broadwell"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-MrBurns-2013-06-12T18:22:00.000Z","type":"heading","level":0,"id":"h-Haswell\/Broadwell-2013-06-12T18:22:00.000Z","replies":["c-MrBurns-2013-06-12T18:22:00.000Z-Haswell\/Broadwell"],"text":"Haswell\/Broadwell","linkableTitle":"Haswell\/Broadwell"}-->

I updated the template, because Haswell is available, so the Haswell/Broadwell section is not in "future" anymore, but Broadwell is not available yet, so it would be better to split t6he Haswell/Broadwell section so that Broadwell is in the future secition and Haswell not, but I don't know how to do that without making two sections with different titles out of the Haswell/Broadwell section (which would not be good, because it would not be clear anymore, that Broadwell is a die-shrink of Haswell). --MrBurns (talk) 18:22, 12 June 2013 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2013-06-12T18:22:00.000Z","author":"MrBurns","type":"comment","level":1,"id":"c-MrBurns-2013-06-12T18:22:00.000Z-Haswell\/Broadwell","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-A5b-2013-10-09T18:28:00.000Z","type":"heading","level":0,"id":"h-Intel_Quark-2013-10-09T18:28:00.000Z","replies":["c-A5b-2013-10-09T18:28:00.000Z-Intel_Quark"],"text":"Intel Quark","linkableTitle":"Intel Quark"}-->

Intel Quark

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-A5b-2013-10-09T18:28:00.000Z","type":"heading","level":0,"id":"h-Intel_Quark-2013-10-09T18:28:00.000Z","replies":["c-A5b-2013-10-09T18:28:00.000Z-Intel_Quark"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-A5b-2013-10-09T18:28:00.000Z","type":"heading","level":0,"id":"h-Intel_Quark-2013-10-09T18:28:00.000Z","replies":["c-A5b-2013-10-09T18:28:00.000Z-Intel_Quark"],"text":"Intel Quark","linkableTitle":"Intel Quark"}-->

Hello. There is new line of SoCs from Intel, Intel Quark. Can anybody add link to Quark to the template? ``a5b (talk) 18:28, 9 October 2013 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2013-10-09T18:28:00.000Z","author":"A5b","type":"comment","level":1,"id":"c-A5b-2013-10-09T18:28:00.000Z-Intel_Quark","replies":["c-Oneiros-2013-10-19T14:36:00.000Z-A5b-2013-10-09T18:28:00.000Z"]}}-->

  •  Done--Oneiros (talk) 14:36, 19 October 2013 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2013-10-19T14:36:00.000Z","author":"Oneiros","type":"comment","level":2,"id":"c-Oneiros-2013-10-19T14:36:00.000Z-A5b-2013-10-09T18:28:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Vossanova-2014-08-06T21:26:00.000Z","type":"heading","level":0,"id":"h-Microarchitecture_consolidation-2014-08-06T21:26:00.000Z","replies":["c-Vossanova-2014-08-06T21:26:00.000Z-Microarchitecture_consolidation"],"text":"Microarchitecture consolidation","linkableTitle":"Microarchitecture consolidation"}-->

Microarchitecture consolidation

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Vossanova-2014-08-06T21:26:00.000Z","type":"heading","level":0,"id":"h-Microarchitecture_consolidation-2014-08-06T21:26:00.000Z","replies":["c-Vossanova-2014-08-06T21:26:00.000Z-Microarchitecture_consolidation"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Vossanova-2014-08-06T21:26:00.000Z","type":"heading","level":0,"id":"h-Microarchitecture_consolidation-2014-08-06T21:26:00.000Z","replies":["c-Vossanova-2014-08-06T21:26:00.000Z-Microarchitecture_consolidation"],"text":"Microarchitecture consolidation","linkableTitle":"Microarchitecture consolidation"}-->

Since most of the CPU/SoC code names linked in this template redirect to their corresponding microarchitecture articles, I think the code name lists should be removed, and the microarchitecture groups merged into a single list -- or perhaps one list for desktop and another for mobile. I'm not against having a convenient list of code names, but without unique page links, they should go in List of Intel CPU microarchitectures instead. Any objectives or alternative suggestions? --Vossanova o< 21:26, 6 August 2014 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2014-08-06T21:26:00.000Z","author":"Vossanova","type":"comment","level":1,"id":"c-Vossanova-2014-08-06T21:26:00.000Z-Microarchitecture_consolidation","replies":["c-Vossanova-2014-08-06T21:30:00.000Z-Vossanova-2014-08-06T21:26:00.000Z"]}}-->

Actually, I just realized Template:Intel processor roadmap exists, and serves this purpose well. --Vossanova o< 21:30, 6 August 2014 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2014-08-06T21:30:00.000Z","author":"Vossanova","type":"comment","level":2,"id":"c-Vossanova-2014-08-06T21:30:00.000Z-Vossanova-2014-08-06T21:26:00.000Z","replies":["c-192.55.54.40-2014-09-13T11:32:00.000Z-Vossanova-2014-08-06T21:30:00.000Z"]}}-->
Actually most do not. Most of the newer ones do since those have not been updated with all the dies, etc. but a rather large number of them redirect to sections on brand pages (e.g., all the Xeon cores). Also your edit loses fabrication tech information not to mention breaks the expanded "state" argument passed to this template on many pages where it is invoked. 192.55.54.40 (talk) 11:32, 13 September 2014 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2014-09-13T11:32:00.000Z","author":"192.55.54.40","type":"comment","level":3,"id":"c-192.55.54.40-2014-09-13T11:32:00.000Z-Vossanova-2014-08-06T21:30:00.000Z","replies":["c-Vossanova-2014-09-16T17:31:00.000Z-192.55.54.40-2014-09-13T11:32:00.000Z"]}}-->
This template is a navigation template, which means its purpose is to link to related articles. The individual cores do not have their own articles, so those links serve no purpose. The navigation template is not meant to add new info (cores, fab size) - just to link to articles. Per WP, "They should be kept small in size as a large template has limited navigation value" If you want an easy reference to such info, you can create a new article and link to it, or edit the existing processor roadmap template. --Vossanova o< 17:31, 16 September 2014 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2014-09-16T17:31:00.000Z","author":"Vossanova","type":"comment","level":4,"id":"c-Vossanova-2014-09-16T17:31:00.000Z-192.55.54.40-2014-09-13T11:32:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Kissg-2015-08-16T09:56:00.000Z","type":"heading","level":0,"id":"h-Skylake_is_not_future_any_more-2015-08-16T09:56:00.000Z","replies":["c-Kissg-2015-08-16T09:56:00.000Z-Skylake_is_not_future_any_more"],"text":"Skylake is not future any more","linkableTitle":"Skylake is not future any more"}-->

Skylake is not future any more

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Kissg-2015-08-16T09:56:00.000Z","type":"heading","level":0,"id":"h-Skylake_is_not_future_any_more-2015-08-16T09:56:00.000Z","replies":["c-Kissg-2015-08-16T09:56:00.000Z-Skylake_is_not_future_any_more"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Kissg-2015-08-16T09:56:00.000Z","type":"heading","level":0,"id":"h-Skylake_is_not_future_any_more-2015-08-16T09:56:00.000Z","replies":["c-Kissg-2015-08-16T09:56:00.000Z-Skylake_is_not_future_any_more"],"text":"Skylake is not future any more","linkableTitle":"Skylake is not future any more"}-->

I tried to update the template myself but it is too complex for me. --Kissg (talk) 09:56, 16 August 2015 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2015-08-16T09:56:00.000Z","author":"Kissg","type":"comment","level":1,"id":"c-Kissg-2015-08-16T09:56:00.000Z-Skylake_is_not_future_any_more","replies":[]}}-->

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Pizzahut2-2019-01-17T20:17:00.000Z","type":"heading","level":0,"id":"h-Microarchitectures_\/_Atom-2019-01-17T20:17:00.000Z","replies":["c-Pizzahut2-2019-01-17T20:17:00.000Z-Microarchitectures_\/_Atom"],"text":"Microarchitectures \/ Atom","linkableTitle":"Microarchitectures \/ Atom"}-->

Microarchitectures / Atom

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Pizzahut2-2019-01-17T20:17:00.000Z","type":"heading","level":0,"id":"h-Microarchitectures_\/_Atom-2019-01-17T20:17:00.000Z","replies":["c-Pizzahut2-2019-01-17T20:17:00.000Z-Microarchitectures_\/_Atom"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Pizzahut2-2019-01-17T20:17:00.000Z","type":"heading","level":0,"id":"h-Microarchitectures_\/_Atom-2019-01-17T20:17:00.000Z","replies":["c-Pizzahut2-2019-01-17T20:17:00.000Z-Microarchitectures_\/_Atom"],"text":"Microarchitectures \/ Atom","linkableTitle":"Microarchitectures \/ Atom"}-->

So I made a note which architectures belong to the Atom line, but it may be better to make a subsection instead.--Pizzahut2 (talk) 20:17, 17 January 2019 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-01-17T20:17:00.000Z","author":"Pizzahut2","type":"comment","level":1,"id":"c-Pizzahut2-2019-01-17T20:17:00.000Z-Microarchitectures_\/_Atom","replies":["c-Vossanova-2019-01-17T21:45:00.000Z-Pizzahut2-2019-01-17T20:17:00.000Z"]}}-->

Yeah, a subsection would be better. --Vossanova o< 21:45, 17 January 2019 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2019-01-17T21:45:00.000Z","author":"Vossanova","type":"comment","level":2,"id":"c-Vossanova-2019-01-17T21:45:00.000Z-Pizzahut2-2019-01-17T20:17:00.000Z","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-DSKoch-2022-05-14T08:10:00.000Z","type":"heading","level":0,"id":"h-Semi-protected_edit_request_on_14_May_2022-2022-05-14T08:10:00.000Z","replies":["c-DSKoch-2022-05-14T08:10:00.000Z-Semi-protected_edit_request_on_14_May_2022"],"text":"Semi-protected edit request on 14 May 2022","linkableTitle":"Semi-protected edit request on 14 May 2022"}-->

Semi-protected edit request on 14 May 2022

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-DSKoch-2022-05-14T08:10:00.000Z","type":"heading","level":0,"id":"h-Semi-protected_edit_request_on_14_May_2022-2022-05-14T08:10:00.000Z","replies":["c-DSKoch-2022-05-14T08:10:00.000Z-Semi-protected_edit_request_on_14_May_2022"]}}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-DSKoch-2022-05-14T08:10:00.000Z","type":"heading","level":0,"id":"h-Semi-protected_edit_request_on_14_May_2022-2022-05-14T08:10:00.000Z","replies":["c-DSKoch-2022-05-14T08:10:00.000Z-Semi-protected_edit_request_on_14_May_2022"],"text":"Semi-protected edit request on 14 May 2022","linkableTitle":"Semi-protected edit request on 14 May 2022"}-->

Change [[Intel Core|Core]] to [[Intel Core#Core|Core]] in "Discontinued", "IA-32 (32-bit)". DSKoch (talk) 08:10, 14 May 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-05-14T08:10:00.000Z","author":"DSKoch","type":"comment","level":1,"id":"c-DSKoch-2022-05-14T08:10:00.000Z-Semi-protected_edit_request_on_14_May_2022","replies":["c-Pppery-2022-05-14T21:59:00.000Z-DSKoch-2022-05-14T08:10:00.000Z"]}}-->

 Done * Pppery * it has begun... 21:59, 14 May 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2022-05-14T21:59:00.000Z","author":"Pppery","type":"comment","level":2,"id":"c-Pppery-2022-05-14T21:59:00.000Z-DSKoch-2022-05-14T08:10:00.000Z","replies":[],"displayName":"* Pppery *"}}-->