Products Group GM Rick Bergman Leaves AMDby Anand Lal Shimpi on September 22, 2011 5:21 PM EST
For the first time in years AMD is set to really start executing on the CPU side. Although Bulldozer has faced significant delays, Brazos and Llano were both warmly received and all indications point to Trinity showing up in early 2012 with even more competitive performance than Llano. AMD has also committed to a 12-month cadence for all of its major product lines, meaning we'll see significant updates to APUs and GPUs yearly.
In the midst of what could very well be AMD's turnaround on the CPU side, its current Products Group General Manager, Rick Bergman, has announced that he is leaving the company. As always no real details are provided but Rick was instrumental in helping stage ATI's comeback as a player in the GPU space if you recall from The RV770 Story.
Bergman will be sorely missed at AMD. Hopefully he won't stray too far from this industry though.
Source: AMD, eWeek, Tech Report
Post Your CommentPlease log in or sign up to comment.
View All Comments
nezuko - Thursday, September 22, 2011 - linkFirst Dirk, and now Rick? OMG, what will AMD become in the future?
IlllI - Friday, September 23, 2011 - linkHP
saneblane - Thursday, September 22, 2011 - linkAmd can't be losing there best talents like this, first dirk and now rick. these aren't guys that can just be simply replaced they have more experienced and have been top of their field for a long time. Dirk was responsible for the team that gave Amd the come back against Intel and rich help bring ATI from the brink of destruction. The CEO seems like a pushover who the board can tell him what they like and i suspect that's the real reason why they picked him. Bulldozer better be good, or AMD is finished.
GiantPandaMan - Friday, September 23, 2011 - linkThey may be just fine. After all, they've been working a lot of talent up their ranks.
I just hope they aren't like all the other stupid companies and hire some hotshot from outside who has no clue on how to run a company as specialized as AMD. (IE-Do not pull an HP!) If they stick to very good managers that have learned the company from the ground up they'll do fine.
davethejackal - Friday, September 23, 2011 - link"I just hope they aren't like all the other stupid companies and hire some hotshot from outside who has no clue on how to run a company as specialized as AMD."
You mean the sort of bozo who might wade in there cancelling the Komodo chip and Corona platform, seemingly without reason?
Ok so there might be good reasons, but it seems too closely timed to the above to be unrelated.
Operandi - Friday, September 23, 2011 - linkIt seems like Komodo was going to be a pretty big CPU, up to 10 cores and all. AMD won't have 22nn ready in time and may have decided against pouring resources into a such a chip when they would be at a process disadvantage with Intel.
dfghdfshhh - Friday, September 23, 2011 - linkCome go and see, will not regret it Oh look
Veroxious - Saturday, September 24, 2011 - linkWhy the reliance on Bulldozer which IMO is pointless in light of the fact that when it launches Intel is on the brink of launching Ivy Bridge which will most certainly destroy Bulldozer. With the short lead time why did AMD not make Bulldozer on 22nm silicon? Maybe that's why heads are rolling???
AG4101997 - Sunday, September 25, 2011 - linkYou want more delays? Ivy is just SB with a smaller die. Not much of a performance boost (around 20% performance boost), and not something to upgrade for if you already have a high-end SB CPU. For all we know, BD may perform well compared to Ivy, but not by much. And you do realize AMD already has plans for a 22nm silicon? They plan on releasing it in 2013 though, a year after Ivy.
Veroxious - Tuesday, September 27, 2011 - linkI know it is very risky introducing new architecture in conjunction with a die shrink but seeing how far behind the curve they are they really have no choice. When AMD goes 22nm then intel's next architecture will be ready so unless they go all in AMD will always be trailing behind.