Talk:Excavator (microarchitecture)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

No Excavator FX CPUs?[edit]

Possibly no excavator FX CPUs? • SbmeirowTalk • 05:32, 4 December 2013 (UTC)[reply]

Yeah, it seems that FX CPU-only parts are dead. Vishera will be the last offering for AM3+. Since there won't be any new sockets besides FM2+, the only way for FX to return (it's just a branding, after all) is on that socket, but currently there's no indications of that happening right now. NarooN (talk) 08:23, 11 December 2013 (UTC)[reply]

editing the chart and correct the typos[edit]

Carrizo and not Carizzo, nm units are in the front row, ...

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 2 external links on Excavator (microarchitecture). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 02:40, 26 September 2017 (UTC)[reply]