Preventing Espionage at AMD: How The Eyefinity Project Came to Be

There’s one more thing Carrell Killebrew has done for the world. He’s single handedly responsible for getting Eyefinity included in the Evergreen stack.

It started like this. All GPU vendors go to their customers (OEMs) and ask them for features they’d like to have. The notebook vendors wanted a total of 6 display outputs from the GPU, although they only needed two to be active at the same time. Two paths could be used for LCD panels, two could be used for external outputs (VGA + DVI/HDMI) and two routed to a docking station connector.

Carrell thought it would be a shame to have all of these output pins but not be able to drive all six at the same time. So he came up with a plan to be able to drive at least 3 displays on any Evergreen card. The high end cards would support 6 displays simultaneously.

His desire to do this wasn’t born out of pure lunacy, Carrell does have a goal in mind. Within the next 6 years he wants to have a first generation holodeck operational. A first generation holodeck would be composed of a 180 degree hemispherical display with both positionally and phase accurate sound. We’ll also need the pixel pushing power to make it all seem lifelike. That amounts to at least 100 million pixels (7 million pixels for what’s directly in front of you, and the rest for everything else in the scene), or almost 25 times the number of pixels on a single 30” display.

We’re not quite at 2016, so he had to start somewhere. And that somewhere happened to be with enabling a minimum of 3 and a maximum of 6 displays, per card, for all members of the Evergreen family. Today we know the technology as Eyefinity, but internally Carrell called it SunSpot.

Carrell didn’t want anyone knowing about SunSpot, so he kept it off the Cypress PRS. Through some very clever maneuvering he managed to keep it off of the radar while engineering hammered out the PRS, and even managed to keep it off of the chopping block when the GPU was cut down in size. He knew that if anyone got wind of it, they’d ask him to kill it while the chip was being scaled down. To make matters worse, if anyone outside of a trusted few became aware of it - there was the chance that NVIDIA would have time to copy and implement the feature. It then became Carrell’s goal to keep SunSpot as quiet as possible.

It began with a list. On this list were names of people who needed to know about SunSpot. If your name wasn’t on the list not only did you not know about SunSpot, but no one who knew about the project was allowed to talk about it near you. There was an internal website created that had the names of everyone who needed to know about SunSpot.

Along with the list, came rules.

As I just mentioned, no one on the list could talk about SunSpot in a place where someone not on the list could overhear. And if you wanted to get someone added to the list, it had to be approved - the final say was in the hands of none other than Carrell Killebrew.

The SunSpot engineers went to work on the feature, bringing in others only when absolutely necessary. The team grew one person at a time and eventually plateaued. The software engineers weren’t made aware of SunSpot until the last minute. Carrell only gave them enough time to enable SunSpot, they didn’t get the luxury of advance knowledge.

Carrell went to David Glenn, head of software engineering at ATI and asked him what the latest possible date that they needed to have someone in software working on this stuff. David gave him a date. Carrell asked for a list of names of people who needed to know. David gave him three names. On that date, the SunSpot team called up those three people and said “we need to tell you something”. Needless to say, no one was happy about Carrell’s secrecy. Some of the higher ups at ATI knew Carrell had people working on something, they just had no idea what it was.


It's the software that ultimately made Eyefinity

When in his own cube Carrell always spoke about SunSpot in code. He called it feature A. Carrell was paranoid, and for good reason. The person who sat on the other side of Carrell’s cube wall left to work for NVIDIA a couple months into the SunSpot project. In all, ATI had three people leave and work for NVIDIA while SunSpot was going on. Carrell was confident that NVIDIA never knew what was coming.

Other than the obvious, there was one real problem with Carrell’s secrecy. In order for Eyefinity to work, it needed support from external companies. If you’ll remember back to the Radeon HD 5800 series launch, Samsung announced thin-bezel displays to be sold in 1, 3 or 6 panel configurations specifically for Eyefinity setups. There was no way to keep SunSpot a secret while still talking to OEMs like Samsung, it’s just too big of a risk. The likelihood of someone within ATI leaking SunSpot to NVIDIA is high enough. But from an employee for an OEM that deals with both companies? That’s pretty much guaranteed.

For a feature like SunSpot to go completely unnoticed during the development of a GPU is unheard of. Carrell even developed a rating system. The gold standard is launch; if SunSpot could remain a secret until the launch, that’s gold. Silver is if they can keep it a secret until they get chips back. And the effort would get a bronze if they could keep it a secret up to tape out, at that point NVIDIA would be at least one full product cycle behind ATI.

Eventually, Rick Bergman, GM of graphics at AMD, committed to keeping SunSpot a secret until bronze, but he told Carrell that when they got to tape out they were going to have a serious talk about this.

Time went on, SunSpot went on, Carrell and crew made it to bronze. The chip had taped out and no one knew about Carrell’s pet project. It got a little past bronze and Rick asked Carrell to have that talk. There were three customers that would really benefit from talking to them about SunSpot, then the killer: it would also help ATI competitively.

Carrell didn’t want to risk tipping off the competition to SunSpot, but he knew that in order to make it successful he needed OEMs on board. The solution was to simply add those at the OEMs who needed to know about SunSpot to the list. The same rules applied to them, and they were given a separate NDA from existing NDAs in place between AMD and the OEM. AMD legal treated SunSpot as proprietary IP, if anyone else within an OEM needed to know about it they needed to first ask for permission to discuss it. To make sure that any leaks would be traceable, Carrell called SunSpot a different name to each of the three OEMs involved.

A few weeks prior to the Cypress launch one of the CEOs at one of the OEMs saw Eyefinity and asked to show it to someone else. Even the CEO’s request needed to be approved before he could share. Surprisingly enough, each of the three OEMs abided by their agreement - to Carrell’s knowledge the tech never leaked.


NVIDIA's Surround driven off two cards

While NVIDIA demonstrated its own triple-display technology at this year’s CES, it’s purely a software solution; each GPU is still only limited to two display outputs. I asked Carrell what he thought about NVIDIA’s approach, he was honest as always.


Eyefinity allows for 3 outputs from a single GPU

ATI considered a software only approach a while ago, but ultimately vetoed it for a couple of reasons. With the software-only solution you need to have a multi-GPU capable system. That means a more expensive motherboard, a more powerful PSU and a little more hassle configuration wise. Then there were the performance concerns.

One scenario is that you have very noticeable asymmetry as you have one card driving one display and the other card driving two displays. This can cause some strange problems. The other scenario is that you have all three displays coming off of a single card, and in alternating frames you send display data from one GPU to the next either via PCIe or a CF/SLI connector. With 6 displays, Carrell was concerned that there wouldn’t be enough bandwidth to do that fast enough.

There were also game compatibility concerns that made ATI not interested in the software approach. Although I was quick to point out that FOV and aspect ratio issues are apparent in many games today with Eyefinity. Carrell agreed, but said that it’s a lot better than they expected - and better than it would have been had they used a software-only solution.

Not to belittle the efforts of ATI’s software engineers here. While Carrell was one of three people originally responsible for SunSpot, they weren’t the ones who made it great. In Carrell’s own words “In the end, I’d say the most key contributions came from our Software engineering team. SunSpot is more a software feature than a hardware one”. ATI’s software team, despite not being clued into the project until it was implemented in hardware, was responsible for taking SunSpot and turning it into Eyefinity.

As for the ridiculous amount of secrecy that surrounded SunSpot? It wasn’t just to keep Carrell entertained. AMD has since incorporated much of Carrell’s brand of information compartmentalization into how it handled other upcoming features. I have to wonder if Carrell somehow managed to derive Apple’s equation for secrecy.

The Payoff: How RV740 Saved Cypress Final Words
Comments Locked

132 Comments

View All Comments

  • Spoelie - Thursday, February 18, 2010 - link

    phoronix.com
    for all things ATi + Linux
  • SeanHollister - Monday, February 15, 2010 - link

    Fantastic work, Anand. It's so difficult to make pieces like this work without coming across as puffery, but everything here feels genuine and evenhanded. Here's hoping for similar articles featuring individuals at NVIDIA, Intel and beyond in the not-too-distant future.
  • boslink - Monday, February 15, 2010 - link

    Just like many others i'm also reading/visiting anandtech for years but this article made me register just to say damn good job.

    Also for the long time i didn't read article from cover to cover. Usually i read first page and maybe second (enough to guess what's in other pages) and than skip to conclusions.

    But this article remind us that Graphic card/chip is not only silicon. Real people story is what makes this article great.

    Thanks Anand
  • AmdInside - Monday, February 15, 2010 - link

    Great article as usual. Sunspot seems like the biggest non-factor in the 5x00 series. Except for hardware reviews sites which have lots of monitors lying around, I just don't see a need for it. It is like NVIDIA's 3D Vision. Concept sounds good but in general practice, it is not very realistic that a user will use it. Just another check box that a company can point to to an OEM and say we have it and they don't. NVIDIA has had Eyefinity for a while (SLI Mosaic). It just is very expensive since it is targeted towards businesses and not consumers and offers some features Eyefinity doesn't offer.I think NVIDIA just didn't believe consumers really wanted it but added it afterwards just so that ATI doesn't have a checkbox they can brag about. But NVIDIA probably still believes this is mainly a business feature.

    It is always interesting to learn how businesses make product decisions internally. I always hate reading interviews of PR people. I learn zero. Talk to engineers if you really want to learn something.
  • BelardA - Tuesday, February 16, 2010 - link

    I think the point of Eyefinity is that its more hardware based and natural... not requiring so much work from the game publisher. A way of having higher screen details over a span of monitors.

    A few games will actually span 2 or 3 monitors. Or some will use the 2nd display as a control panel. With Eyefinity, it tells the game "I have #### x #### pixels" and auto divides the signal onto 3 or 6 screens and be playable. That is quite cool.

    But as you say, its a bit of a non-factor. Most users will still only have one display to work with. Hmmm. there was a monitor that was almost seamless 3-monitors built together, where is that?

    Also, I think the TOP-SECRET aspect of Sun-Spots was a way of testing security. Eyefinity isn't a major thing... but the hiding of it was.

    While employees do move about in the business, the sharing of trade-secrets could still get them in trouble - if caught. It does happen, but how much?
  • gomakeit - Monday, February 15, 2010 - link

    I love these insightful articles! This is why Anandtech is one of my favorite tech sites ever!
  • Smell This - Monday, February 15, 2010 - link

    Probably could have done without the snide reference to the CPU division at the end of the article - it added nothing and was a detraction from the overall piece.

    It also implies a symbiotic relationship between AMDs 40+ year battle with Chipzilla and the GPU Wars with nV. Not really an accurate correlation. The CPU division has their own headaches.

    It is appropriate to note, however, that both divisions must bring their 'A' Game to the table with the upcoming convergence on-die of the CPU-GPU.
  • mrwilton - Monday, February 15, 2010 - link

    Thank you, Anand, for this great and fun-to-read article. It really has been some time where I have read an article cover to cover.

    Keep up the excellent work.

    Best wishes, wt
  • Ananke - Monday, February 15, 2010 - link

    I have 5850, it is a great card. However, what people saying about PC gaming is true - gaming on PC slowly fades towards consoles. You cannot justify several thousand-dollar PC versus a 2-300 multimedia console.

    So powerful GPU is a supercomputer by itself. Please ATI, make better Avivo transcoder, push open software development using Steam further. We need many applications, not just Photoshop and Cyberlink. We need hundreds, and many free, to utilize this calculation power. Then, it will make sense to use this cards.
  • erple2 - Tuesday, February 16, 2010 - link

    Perhaps. However, this "PC Gaming is being killed off by the 2-300 multimedia console" war has been going on since the Playstation 1 came out. PC gaming is still doing very well.

    I think that there will always be some sort of market (even if only 10% - that's significant enough to make companies take notice) for PC Gaming. While I still have to use the PC for something, I'll continue to use it for gaming, as well.

    Reading the article, I find it poignant that the focus is on //execution// rather than //ideas//. It reminds me of a blog written by Jeff Atwood (http://www.codinghorror.com/blog/2010/01/cultivate...">http://www.codinghorror.com/blog/2010/01/cultivate... if you're interested) about the exact same thing. Focus on what you //do//. Execution (ie "what do we have an 80%+ chance of getting done on time) is more important than the idea (ie features you can claim on a spec sheet).

    As a hardware developer (goes the same for any software developer), your job is to release the product. That means following a schedule. That means focusing on what you can do, not on what you want to do. It sounds to me like ATI has been following that paradigm, which is why they seem to be doing so well these days.

    What's particularly encouraging about the story written was that Management had the foresight to actually listen to the technical side when coming up with the schedules and requirements. That, in and of itself, is something that a significant number of companies just don't do well.

    It's nice to hear from the internal wing of the company from time to time, and not just the glossy presentation of hardware releases.

    I for one thoroughly enjoyed the read. I liked the perspective that the RV5-- err Evergreen gave on the process of developing hardware. What works, and what doesn't.

    Great article. Goes down in my book with the SSD and RV770 articles as some of the best IT reads I've done.

Log in

Don't have an account? Sign up now