upnorthsox
Veteran
Clearly.@BRiT AMD planned for RDNA2 to come out this year, and Microsoft announced an RDNA2 based product this year, so we all know what the most obvious conclusion is ... Microsoft is clearly LYING.
Clearly.@BRiT AMD planned for RDNA2 to come out this year, and Microsoft announced an RDNA2 based product this year, so we all know what the most obvious conclusion is ... Microsoft is clearly LYING.
In your request to be reasonable, the quote you are referencing:Sure but that isn’t how we announce things publicly in marketing statements. Nor do I expect under any reasonable condition that odium can produce driver statements indicating that both are 1.9.
Be reasonable here; the probability extremely low
I don't see under any reasonably reading of this you can come up with him calling it a definitive version number or that he is or represents himself as part of any marketing statement.* Both systems are rdna 2, but not. They are essentially rdna 1.9 so to speak, with features bolted on, meaning that you can call it the next generation of rdna, you could even call it rdna 2 if you wanted. I wouldn’t myself but that seems to be what they are doing so ok.
And exactly how is he qualifying this statement if no RDNA2.0 architecture is out there right now?In your request to be reasonable, the quote you are referencing:
I don't see under any reasonably reading of this you can come up with him calling it a definitive version number or that he is or represents himself as part of any marketing statement.
A reasonable reading would be that he saying it's close but not quite RDNA2 but if you want to call it RDNA2 then that's fine.
On first glance one would assume it means it's 0.1 less. However, the guy who wrote it never established which numeral system he was using and were there any conversions to other systems on the way, so the real difference is anyone's guessCan’t wait to read the next few hundred pages of discussions over what exactly 1.9 means versus 2, based on what some guy somewhere wrote. Riveting stuff.
I'm done with it so don't worry, there will be no debate, you'll be fast forwarded to previews about XSX using Zen 1.5, we'll circle back to 12 TF GCN 4.7 flops.Can’t wait to read the next few hundred pages of discussions over what exactly 1.9 means versus 2, based on what some guy somewhere wrote. Riveting stuff.
Would AMD really want someone misrepresenting their product as RDNA2 if it's not actually RDNA2? Doubtful. If Microsoft announced it as RDNA2, and it fits the timeline of AMD releasing RDNA2, then that's likely what it is.
The gpu isn't yet self-aware, don't tell the enclosure what it can do with it's body!A GPU can self identify as it sees fit! We’re in 2020 guys, let GPUs be their true self. Even if it feels like a CPU, then who are we to judge?
AMD will even let them call it RDNA 99 SUPER-ADVANCED XT, as long as Microsoft pays for it.Would AMD really want someone misrepresenting their product as RDNA2 if it's not actually RDNA2? Doubtful. If Microsoft announced it as RDNA2, and it fits the timeline of AMD releasing RDNA2, then that's likely what it is.
Who wrote RDNA 1.9 when mentioning the SeriesX GPU?all reasonable logic is not prevailing here:
a) marketing materials from MS and their partners at AMD has been officially announced as RDNA 2.0 micro-architecture
b) AMD is the one responsible for determining what is and isn't RDNA2.0
c) we have a person who is not directly involved with the hardware claiming it's not quite RNDA2.0 but has no method of proving this
d) we have a whole bunch of people jumping onto this bandwagon.
Per the amd slide, rdna2=7nm+, right? For some reason some xbox guys are saying xsx is not on 7nm+. (the ~400mm2 die size would agree with them). Would that lack of 7nm+ make it "<rdna2"?Sure but that isn’t how we announce things publicly in marketing statements. Nor do I expect under any reasonable condition that odium can produce driver statements indicating that both are 1.9.
Be reasonable here; the probability extremely low
Which xbox guys? Or do you mean supposed insiders? Cuz there's an easy answer to that conundrum?For some reason some xbox guys are saying xsx is not on 7nm+. (the ~400mm2 die size would agree with them). Would that lack of 7nm+ make it "<rdna2"?
400mm^2 seems to line up nicely with 3 shader engines that are 10 WGP big each, plus 8* Zen2 cores with 8MB L3, plus leeway for additional RT units (which are tiny on Turing, so people are assuming they should also be tiny on RDNA2), memory controller, glue, etc.Which xbox guys? Or do you mean supposed insiders? Cuz there's an easy answer to that conundrum?
It's for their own GPUs, not for the architecture, AMDs architectures aren't tied to specific process or even foundry.Per the amd slide, rdna2=7nm+, right? For some reason some xbox guys are saying xsx is not on 7nm+. (the ~400mm2 die size would agree with them). Would that lack of 7nm+ make it "<rdna2"?
Guess I'm asking if the density increase associated with 7nm+ could be responsible for some of the optimizations rdna2 has over rdna1, besides removing the remaining traces of gcn?
400mm^2 seems to line up nicely with 3 shader engines that are 10 WGP big each, plus 8* Zen2 cores with 8MB L3, plus leeway for additional RT units (which are tiny on Turing, so people are assuming they should also be tiny on RDNA2), memory controller, glue, etc.
The chip being 400mm^2 suggests it's not taking advantage of the 17% area reduction that TSMC's N7+ offers over N7, at which the chip should come at closer to 350mm^2
So you've made a bunch of assumptions and 7nm+ isn't lining up with your assumptions therefore 7nm+ must be wrong?
I don't mean insiders. I mean people who have no problem telling all of twitter and gaf/era that they prefer xbox.Which xbox guys? Or do you mean supposed insiders? Cuz there's an easy answer to that conundrum?
And without knowing the exact contents of that die... how many mm2 in a teraflop?
Thanks.It's for their own GPUs, not for the architecture, AMDs architectures aren't tied to specific process or even foundry.