It is interesting though that the rumored Big Navi clocks are only 2.1GHz. If true, it is an indication that Big Navi is N7 and PS5 is N7+ EUV (or N7P, but I doubt). And then we have N7E for series X, I wonder how difficult or time consuming would be to convert the RDNA2 design to all these processes. With RDNA1 we had 1905MHz for 5700XT, 1845MHz for 5500XT (-3%) and then the comfort zone (a good compromise between performance/W) for the design was at 1750MHz (highest 5600XT designs, mild OC 5700 designs). PS5 2230MHz figure should be the 5500XT RDNA1 clock level equivalent, (judging by the Marc Cerny presentation and the way he frased his comments regarding the clocks) meaning that a classic RDNA2 design AIB in a N7+ EUV process can hit 2,3GHz (2.5GHz air cooled) Since N7+ EUV performance is +10% in relation with N7, then the 2.1GHz clocks should be justified then in N7. Also the +10% perf the EUV design enjoys in relation with plain N7, is in the new TSMC report, before 1 year was at the same performance and before 2,5 years, EUV performance projections in official TSMC reports was worst the N7. N7+ EUV was not so successful as other TSMC's nodes in such designs and it would be logical to assume that TSMC in order to improve the performance of the node so much in the last year should have in volume production a design and a partner such as Sony and PS5, it fits somehow. Also if Sony wanted to have the option to migrate in a later phase of the console life to smaller EUV process it would be easier I would assume. Anyway, enough with the speculations, but a classic 2.1GHz RDNA2 design with just 5% IPC improvements, 128 RBEs , 8 primitives and 80CUs with enough bandwidth to feed the RBEs (1TB/s) it would be past 3080 by more than 10% easily. I really don't know what to think about the rumored 256bit memory bus/128RBEs and 128MB cache design, lol the ArtX dream lives on, we will see.