Leaked Richland specs reveal higher clock speeds

Richland, AMD's upcoming successor to Trinity, is already shipping to PC makers. The updated silicon has been tuned to offer lower power consumption and higher clock speeds, and it will come with a bundle of AMD-branded applications and "optimized" games. Although Richland seems primarily geared toward mobile applications, desktop versions are on the way, and they should slot into existing FM2 motherboards. VR-Zone's Chinese site has now published specifications detailing the purported particulars of those desktop chips.

Model Cores Clock speed Radeon HD TDP
Base Turbo Model Clock speed
A10-6800K 4 4.1GHz 4.4GHz 8670D 844MHz 100W
A10-6700 4 3.7GHz 4.3GHz 8670D 844MHz 65W
A8-6600K 4 3.9GHz 4.2GHz 8570D 844MHz 100W
A8-6500 4 3.5GHz 4.1GHz 8570D 800MHz 65W
A6-6400K 2 3.9GHz 4.1GHz 8470D 800MHz 65W
A6-6300 2 3.7GHz 3.9GHz 8370D 760MHz 65W

Don't get too excited about the 8000-series model numbers for the integrated Radeons. Richland's GPU is based on the same Radeon HD 6000-series foundation as Trinity's integrated graphics. GPU clock speeds are a little higher in Richland, but the deltas are less than 100MHz.

If the published specifications are accurate, desktop-bound versions of Richland have received a nice boost in CPU clock speeds. The base clocks are 300MHz higher than in equivalent Trinity processors, and Turbo speeds are up 200-400MHz. Those increases don't appear to have affected Richland's TDP, which is still either 65W or 100W, depending on the model. The unlocked K-series chips are the only ones with 100W TDPs.

Trinity isn't the most compelling desktop product, but Richland should at least be an improvement. The new APU only needs to tide us over until later this year, when Kaveri is expected to arrive with updated integrated graphics based on the current GCN architecture. Kaveri will be fabbed on a 28-nm process, a shrink from the 32-nm node used to manufacture Trinity and Richland APUs.

Tip: You can use the A/Z keys to walk threads.
View options

This discussion is now closed.