Monday, September 12th 2022
Robert Hallock Announces His Departure from AMD
AMD's Technical Marketing Director, Robert Hallock has decided to leave the company after 12+ years with the company, to "explore new opportunities and experiences" as he puts in a post on LinkedIn. He apparently left the company last Friday, but only shared the news today. "After just over 12 adventure-packed years at AMD, I'm leaving to explore new opportunities and experiences. Over the years, I've had the honor and privilege of publicly teaching others about some truly stellar innovation: the Zen core family, 3D V-Cache, chiplet packaging, HBM memory, FreeSync, low-overhead graphics APIs, and much more. After working in both graphics and processors for roughly 6 years each, I've learned so much."
He thanked several current and ex colleagues at AMD, as well as thanking the PC hardware reviewer community and the AMD community on Reddit and Discord among others. He ended his post by saying he'll be taking some time off to travel and think about what he'll be doing next, so it doesn't seem like he has any fixed plans for the future.
Source:
Robert Hallock on LinkedIn
He thanked several current and ex colleagues at AMD, as well as thanking the PC hardware reviewer community and the AMD community on Reddit and Discord among others. He ended his post by saying he'll be taking some time off to travel and think about what he'll be doing next, so it doesn't seem like he has any fixed plans for the future.
45 Comments on Robert Hallock Announces His Departure from AMD
But Hallock was responsible for some disinformation in the Zen 2 era, where he "applied" (on a blackboard) a PBO+ 200 MHz overclock on top of boost frequency, and then none could achieve anything remotely similar, not even with custom water cooling. Of course it was excused "just as an example".
The first manager I worked under as a graduate put in his resignation and said he was "taking a big break to spend time with his family". Everyone was patting him on the back for being such a great family man. A few months later there was word spreading around the office of a competing firm that had just recently started up and......guess who was at the helm. Family man himself.
I don't know about you, but for me Robert will remain as _unattainable_4.75GHz_Ryzen3000_ (on first wave of Zen2 - so exactly).
What made it so?
A flaw? Misunderstanding? Deception, after all?
Who knows, but what makes the most sense to the average consumer in the end?
The fact, that he didn't get what was claimed.
And now? Now we're waiting what the 7950X's "up to 5.7 GHz" boost clock, or "5.85 GHz Fmax" even means. We're fine with that Ryzen's can't perform any task at boost frequency, not even a purely synthetic single thread one. Sure, we need performance, frequency by itself is quite meaningless. But how do we know our very expensive CPU is performing as advertised? Frequency is the only thing advertised, promised.
The 3100 in my HTPC, in the other hand, maintains its 3.9 GHz boost clock all the time, even when all cores are tasked. The 5500 I built my brother's new PC around clocks at a constant 4.25 GHz as well.
AMD then publicly acknowledged there is a bug in AGESA, and prepared the fix. It took quie a bit of time, and some motherboard vendors took even longer then to implement the new bios. Fix was confirmed to have worked in a poll, but later some users reported that subsequent bios releases again lowered the maximum boost frequency - but then there was no activism to confirm or deny that. The same happened with Zen 3, again noone organised wider consumer pressure to fix that.
But as we know, it didn't really matter, Ryzen processors don't perform any meaningful task at boost frequency. It's just a random high frequency CPU boosts to with very light load for a very short time, so it looks good on paper. The performance remained largely the same for processors that boosted properly and the ones that were missing the mark by as much as 200 MHz.
And you don't even care if you get fired for having a Youtube channel. Can't make this $h1t up. Silicon valley seems to be pretty facist.