Thanks for the post . Yea it looks really bad on AMD that these were leaked like that. I have a question fir you .could oberon be the BC test units kept at 36 cu for BC purpose? Something about this chip seems off.it has no vrs, no raytracing etc... i mean if sony is gonna use this chip why are they not laumching in 2019 ?everythung would have been ready for 2019 launch
Yes, I think it's possible, but it is hard to tell for sure. As people are pointing out, it could be that, could be related to an older set of tests, or maybe there is a PS5 Lockhart excuse for a console after all or simply Sony went for a much more conservative approach, which is sad.
I tend to be a realitst and, Occam's Razor applyied, I'm simply leaning towards a 9,2 TF PS5 at the momment.
EDIT: but really, the repo's content is very weird. It's nothing like a bona fide engineer would post publicly. Hell, you don't have to be an engineer to know that you should not mix personal files and random shit with work stuff.
I'm a programmer too (I work for a very small company though, so things can be more chaotic than in a large corporation), and while I mostly try to write sensible commit messages (like $CLIENT-$ISSUE: $EXPLANATION_OF_WHAT_IS_BEING_COMMITED), especially for clients I basically take care of myself alone there can be many commits which are just "prkl" (which is shorthand for "perkele", perhaps the best Finnish swear word). For stupid things like forgetting to commit one file more, or having a typo somewhere.
For a company size of AMD, one should expect more professionalism, no question. But having nonsensical commit messages is hardly unheard of. (this is not to say anything about the validity of that GitHub data, just a general observation)
...oooh, but I just thought of something. What company bought GitHub a little while back? It's tinfoil hat time!
But this is way too much high profile of a work for that behaviour. Most of the commits didn't had any comment, the ones that had just had things like the 'kkkkk'. The code is simple, just a bunch of python scripts for testing, but still, I find it hard to believe that a AMD engineer would structure it that way and leave it publicly available to anyone curious enough to just type "oberon arden" on GitHub's search: no kidding, it was the first hit!