Wednesday, March 19th 2025

AMD "Medusa Point" APU with Zen 6 Confirmed to Use RDNA 3.5, RDNA 4 Reserved for Discrete GPUs
AMD's next-generation Zen 6-based "Medusa Point" mobile APUs will not feature RDNA 4 graphics as previously speculated, according to recent code discoveries in AMD GPUOpen Drivers on GitHub. The Device ID "GfxIp12" associated with RDNA 4 architecture has been reserved only for discrete GPUs, confirming that the current Radeon RX 9000 series will exclusively implement AMD's latest graphics architecture. Current technical documentation indicates AMD will instead extend RDNA 3.5 implementation beyond the Zen 5 portfolio while potentially positioning UDNA as the successor technology for integrated graphics.
The chiplet-based Medusa Point design will reportedly pair a single 12-core Zen 6 CCD manufactured on TSMC's 3 nm-class node with a mobile client I/O die likely built on N4P. This arrangement is significantly different from current monolithic mobile solutions. Earlier speculation indicates the Medusa Point platform may support 3D V-Cache variants, leveraging the same vertical stacking methodology employed in current Zen 5 implementations. The mobile processor's memory controllers and neural processing unit are expected to receive substantial updates. However, compatibility limitations with AMD's latest graphics features, like FSR 4 technology, remain a concern due to the absence of RDNA 4 silicon. The Zen 6-powered Medusa Point processor family is scheduled for release in 2026, targeting premium mobile computing applications with a performance profile that builds upon AMD's current Strix Halo positioning.
Sources:
Kepler_L2, via Wccftech
The chiplet-based Medusa Point design will reportedly pair a single 12-core Zen 6 CCD manufactured on TSMC's 3 nm-class node with a mobile client I/O die likely built on N4P. This arrangement is significantly different from current monolithic mobile solutions. Earlier speculation indicates the Medusa Point platform may support 3D V-Cache variants, leveraging the same vertical stacking methodology employed in current Zen 5 implementations. The mobile processor's memory controllers and neural processing unit are expected to receive substantial updates. However, compatibility limitations with AMD's latest graphics features, like FSR 4 technology, remain a concern due to the absence of RDNA 4 silicon. The Zen 6-powered Medusa Point processor family is scheduled for release in 2026, targeting premium mobile computing applications with a performance profile that builds upon AMD's current Strix Halo positioning.
23 Comments on AMD "Medusa Point" APU with Zen 6 Confirmed to Use RDNA 3.5, RDNA 4 Reserved for Discrete GPUs
Ryzen 5000 series 3 years after the last discrete GPU, and the Ryzen 7000 series 5 years after the last discrete GPU got a couple models with GCN.
Finally isn’t RDNA 3.5 + an NPU + media decoding/encoding units close to RDNA4 anyway. I think there needs to be more context that an architecture number difference.
Specifically here, RDNA 3.5 has been highly optimized for power and bandwidth restrained mobile scenarios.
While it might make us feel better to have RDNA 4 (and FSR 4 would be very welcome in mobile!), unless they have the resources free to make an optimized 'RDNA 4.5', it would probably be a step backwards.
Historically, for every Phoenix or Hawk point sold to someone who actually cares about that there are hundreds sold to business or someone else who doesn't care about that. AMD doesn't have unlimited resources, and APU's is clearly not their cash cow.
Even if they did go for RDNA4, what's the point? Putting all that extra work into something that won't do rays in a meaningful anyway because it's too slow to begin with.
Now who wouldn't want 890M iGPU or even 8060S to be 30% faster? And who wouldn't wan't FSR4 on mobile? The whole point of Strix Halo (and Medusa Halo) is IGP-performance. It's a shame already that Strix Halo is not RDNA4.
Of course, the reason is cost. With only slightly more shaders, the same IF-cache and memory controller, but upgraded architecture, double the L2-cache and PCIe Gen5, Navi48 has nearly double the amount of transistors of Navi32 and nearly as much as Navi31 and can only stay about as big as Navi32 due to more expensive N4-process and highly increased packing densitiy. So upgrading IGPs to RDNA will make them quite a lot more costly to produce, which isn't an option yet. However, just as I would prefer a 9070XT over a 7900XT I would prefer a 9050S with 32CUs RDNA4 over a 8060S with 40CUs RDNA3.5.
I haven't seen talks about a "Medusa Halo" other than minor things from MLID, and I don't think this is a credible source at all.
I bring a valid reason and it's nonsense. Meanwhile, you bring up the fact that the 9070 XT does more work than a 7800 XT (which is RDNA 3, not 3.5). You forgot about power draw, how convenient.
Power draw is everything for mobile devices, and the 9070 XT and the 7900 XTX has identical power draw, about the same performance, and about the same efficiency. HW is vastly different and so is manufacturing cost, but that's a given.
So tell me again, how does an RDNA 4 GPU with a 3 % better efficiency than the RDNA 3 GPU, which is negligible, become a better choice than an RDNA 3.5 GPU, IF it means a lot of extra work for AMD?
Whatever comes after RDNA 4 might be a worthy upgrade for mobile, but this is not it.
And it's not possible - well, possible, but not a good idea - to develop both new cpu + gpu both at the same time. So they just develop a new CPU and slap on whatever existing, proven gpu they have.
The better question is, why does it take so much time to release new desktop APUs? It took 3 years to go from Cezanne to Phoenix. Strix Point is already out but there's no news about any new APUs, not even on leaked roadmaps. Will we have to wait until 2027 for a 8600G successor (which will most likely just be a Strix Point port)?
But I agree that this might be not enough to justify upgrading to RDNA4, since it nearly doubles the transistorcount and thus makes costly N4-node necessary. Yet we know nothing about UDNA, so we can only hope it will be more of an upgrade than RDNA4. That's not entirely true. Phoenix with RDNA3 came out less than five months after RX 7900XT(X), so they were developed rather close together. It's risky but necessary not to fall behind. AMD has some catching up to do GPU-wise. The answer is because desktop-APUs aren't a big market and it's even less important how fast they are. Their only selling point is low price and that's only true for 8400F and 8500G. Even though RAM-OC records are made with Phoenix-APUs right now, there is no real reason to play games on 8700G and invest in fast RAM because 7500F and anything above RX 6400 will be much faster. Only reason is if you really don't have space for anything but the tiniest ITX-cases.
What I don't get is why AMD willingy makes themselves look worse than Intel on everything but halo-laptops by always recycling old APU-generations once or twice. While only the cheapest, lowest-end Intel-laptops come with last generation's CPUs, it is commonplace that in many identical AMD-variants, the refresh of the last generation is used. Compare the last generations of Lenovo Thinkbooks and Thinkpad E- and L-series aswell as HP Probook 400 and Elitebook 600 between Intel and AMD.
While Intel did the same thing this time around - recycling Alder Lake and Raptor Lake as Core 200 without ultra (core i 14000 was a refresh with increased clock and partly corecount atleast), it seems they will be used not nearly as much as the second Phoenix-recyling called AMD Ryzen 200U/H.
They did the right thing by developing a seperate, smaller and cheaper DIE with the same tech as Strix Point with Krakan Point, but now it seems many laptops will be available with two or even three different DIEs.
Indiana Jones on hand held with ray tracing & upscaling is a milestone.
It's the opposite of desktop graphics cards, where pretty much every buyer wants the same things. Yeah, I missed the lack of XT there, but like I tried to explain, none of that matters as we don't know where mobile RDNA 3.5 fits into all this. The decimal part of 3.5 doesn't reflect on whether it's closer to RDNA 3 or 4. It's just something different, optimized for mobile (just like Fouquin said) WTF are you even talking about.
866 days between mobile Cezanneand Phoenix, and 1000 days between AM5 Cezanneand Phoenix. That's 4.5 months longer, is that something to whine about? :roll:
AM5 APU's are not a priority, and with soldered APU's becoming more popular in desktops, that won't change. If you want the best graphics performance out of any Strix you will want soldered LPDDR RAM anyway.
The 128 GB RAM of Strix Halo are not enough to load even the smallest real (=not the "-Distill-" ones are just Qwen / Llama fine-tunes) DeepSeek-R1 quant either. A Strix Halo successor with 256 GB RAM and (at least) double the bandwidth (>500 GB/s) is what many are waiting for. Basically right: It's 304W vs 355W and according to some sources, the power efficiency improved by like 7-15%. According to this (would prefer a test of a non-OC card), it is indeed the same performance (well, 1% difference): If we assume the TDP limit was fully utilized: 355W/304W = 1.168 -> 16.8% and 23% in ray-tracing. Both percentages aren't even generational improvements (if we define a generational improvement between 25% and 33% more FPS per Watt).
I wish Medusa Halo would be double that of Strix Halo. APPLE is offering up to 512 GB RAM in Mac Studio.
Edit: Let me add, why at least 256 GB RAM: According to this (which was posted after my post, but it's kinda common knowledge by now), recommended DeepSeek-V3 / -R1 quants are 2.42bit (203GB) / 2.71bit (231GB) and above.
273 GB/s = 8533 * 64 (bit per channel) * 4 (channels) (64-bit * 4 is where the 256-bit come from) / 8 / 1000.
APPLE's own site also lists 273 GB/s.
MacBook Pro with 48GB RAM (M4 Pro variant, 256-bit) - 3100 $: 273 GB/s.
MacBook Pro with 48GB RAM (M4 Max 16-core variant, 512-bit) - 4000 $: 546 GB/s (= 8533 * 64 * 8 / 8 / 1000).
So, with the same 48GB RAM, the M4 Max variant costs 29% more, but is also double the memory speed.
It also appears that all MacBook Pro M4 Max 48GB, 64GB and 128GB RAM variants have the same memory bandwidth / speeds (to get the same RAM speeds across all RAM size variants, it looks like different densities per LPDDR5(X) chip are used).
Yep, the elephant in the room is the APPLE tax. The 128 GB RAM MacBook Pro costs 5000 bucks.
Basically AMD' Strix Halo and APPLE use the same memory LPDDR5(X) chips, but APPLE's wants 79% (1.79 = 5000 $ / 2800 $) more for the same 128GB RAM capacity.