AMD’s first custom Radeon GPU set to power future Samsung flagships will easily beat the current industry-leading options. That’s what can be inferred from several benchmark summaries leaked out of South Korea. Samsung and AMD originally announced their mobile GPU partnership back in mid-2019, but the first fruits of their collaboration won’t make their way to consumers until at least 2021, AMD previously said.
Following nearly a year of no updates, newly emerged information indicates the project is still on course to hit that tentative release window. AMD is now said to be in the process of optimizing the custom GPU which may be integrated into Samsung’s seminal 5nm silicon.
Exynos 1000 likely to use AMD graphics
Additionally, we finally caught a glimpse of what to expect from the said chipset which will be based on AMD’s RDNA architecture. Looking at the leaked synthetic early test scores originating from GFXBench, the AMD GPU for future Samsung flagships scored 181.8 frames in the Manhattan 3.1 test, which is about 13% greater than what the Adreno 650 found inside Qualcomm’s Snapdragon 865 is capable of. Additionally, it averaged 138.25 and 58 frames in Aztec Normal and Aztec High testing, respectively. These two results are even more significant as they beat Qualcomm’s latest and greatest mobile GPU by a factor of three.
The first AMD Radeon GPU for Galaxy smartphones is likely to make its way to the Exynos 1000, or however the 2021 successor to the Exynos 990 ends up being called. In the meantime, Samsung is also said to be working on a revised 7nm offering after reportedly feeling “humiliated” by Qualcomm’s Snapdragon 865. The SoC, possibly called the Exynos 992, could power the upcoming Galaxy Note 20 series expected to launch in August.
It’s still early days, though, and none of these scores have been independently verified, so it would be best to take this with a grain of salt for now.
The post AMD GPU for 2021 Samsung flagships impresses in first leak appeared first on SamMobile.
from SamMobile https://ift.tt/3bOHKDC
via IFTTT
0 comments: