Plenty of rebrands
AMDs new Radeon Rx 300 series graphics cards are just around the corner and according to new details coming from AMD's recent Catalyst 15.3 Beta driver. Apparently, most of the upcoming Radeon Rx 300 series will be rebrands, just as it was expected and reported earlier.
While there were some rather strange rumors, mostly coming from Wccftech.com, that the entire upcoming AMD Radeon Rx 300 series could be based on completely new GPUs, which was unbelievable, earlier rumors suggesting that Fiji GPU will be the only new GPU in the lineup are looking more and more real.
According to leaked details from AMD's new Catalyst 15.3 Beta driver, spotted by Anandtech.com, AMD's lineup starts with Radeon R9 370 graphics card based on Trinidad GPU, which is pretty much Curacao/Pitcairn GPU under a fancy new name. In case you missed it, Pitcairn GPU was launched back in 2012 as Radeon HD 7870 and its last version is the R9 270(X).
According to Device ID in the new Catalyst 15.3 Beta driver, the R9 360 will be based on Tobago GPU, which is pretty much Bonaire GPU, packing same 896 Stream Processors. The R7 350X, R5 340 and the R5 340X will all be based on a well known entry-level Oland GPU with 384 Stream Processors.
The last but not the least, is the R5 310, based on Caicos GPU, something that you will probably see in a lot of office OEM systems.
Most AMD Rx M300 Mobility series mobile graphics cards will also be rebrands and include Cape Verde, Oland and Topaz GPUs in various stream processor and memory configurations.
As expected, the only really new GPU is the Fiji GPU with High-Bandwidth Memory. The only other unknown is the Tonga XT GPU, the one that we talked about earlier when Radeon R9 285, based on Tonga Pro, was released. We still believe that there is a Tonga XT GPU with 384-bit memory interface and this one should launch with the new Radeon Rx 300 series.
AMD is obviously gearing up for a massive launch and we will know for sure, but according to these information, you should brace yourself for a massive rebrand launch.
Source: Videocardz.com.
While there were some rather strange rumors, mostly coming from Wccftech.com, that the entire upcoming AMD Radeon Rx 300 series could be based on completely new GPUs, which was unbelievable, earlier rumors suggesting that Fiji GPU will be the only new GPU in the lineup are looking more and more real.
According to leaked details from AMD's new Catalyst 15.3 Beta driver, spotted by Anandtech.com, AMD's lineup starts with Radeon R9 370 graphics card based on Trinidad GPU, which is pretty much Curacao/Pitcairn GPU under a fancy new name. In case you missed it, Pitcairn GPU was launched back in 2012 as Radeon HD 7870 and its last version is the R9 270(X).
According to Device ID in the new Catalyst 15.3 Beta driver, the R9 360 will be based on Tobago GPU, which is pretty much Bonaire GPU, packing same 896 Stream Processors. The R7 350X, R5 340 and the R5 340X will all be based on a well known entry-level Oland GPU with 384 Stream Processors.
The last but not the least, is the R5 310, based on Caicos GPU, something that you will probably see in a lot of office OEM systems.
Most AMD Rx M300 Mobility series mobile graphics cards will also be rebrands and include Cape Verde, Oland and Topaz GPUs in various stream processor and memory configurations.
As expected, the only really new GPU is the Fiji GPU with High-Bandwidth Memory. The only other unknown is the Tonga XT GPU, the one that we talked about earlier when Radeon R9 285, based on Tonga Pro, was released. We still believe that there is a Tonga XT GPU with 384-bit memory interface and this one should launch with the new Radeon Rx 300 series.
AMD is obviously gearing up for a massive launch and we will know for sure, but according to these information, you should brace yourself for a massive rebrand launch.
Source: Videocardz.com.
News by Luca Rocchi and Marc Büchel - German Translation by Paul Görnhardt - Italian Translation by Francesco Daghini
Previous article - Next article
comments powered by Disqus
comments powered by Disqus