In the long-running saga of Intel’s conflicts with various national trade commissions, 2009 was a lousy year for Intel. The European Commission fined Intel for nearly 1.5 billion USD, the US Federal Trade Commission sued Intel on anti-trust grounds, and Intel settled with AMD for another 1.25 billion USD. If nothing else it was an expensive year, and while Intel settling with AMD was a significant milestone for the company it was not the end of their troubles.

Now just shy of 9 months after the FTC’s lawsuit began, Intel’s conflicts are starting to come to an end. While the European Commission’s fine is still on appeal, Intel can close the book on their troubles with the FTC: Intel and the FTC have reached a settlement ahead of what would have been next month’s court hearing. With this settlement the FTC is agreeing to drop the case in return for a series of prohibitions and requirements placed upon Intel to maintain and enhance the competitive environment in the CPU and GPU markets. However true to their word, the FTC did not push for any fines – this is a settlement of actions, and not one of greenbacks.


As a quick refresher, the FTC had been investigating Intel for a number of years. Ahead of their suit in December of 2009 the FTC brought Intel to the table and tried to negotiate a settlement, but that didn’t come to pass. In the meantime Intel and AMD reached a separate truce back in November of 2009, an important distinction as AMD had been the primary instigator of all of the investigations against Intel. Ultimately the FTC decided to take their case forward without further help from AMD, a somewhat surprising move that at first glance seems to have largely panned out in the FTC’s favor.

In the suit, the FTC listed a number of complaints towards Intel over both the CPU and the GPU markets, where in the former Intel is the dominant player, and in the latter their market share has been increasing over the years as IGPs grow in popularity. The FTC’s complaints were roughly as follows:


  1. The usual complaints we’ve seen from the EU. Intel rewarded OEMs to not use AMD’s processors through various means, such as volume discounts, withholding advertising & R&D money, and threatening OEMs with a low-priority during CPU shortages.
  2. Intel reworked their compiler to put AMD CPUs at a disadvantage. For a time Intel’s compiler would not enable SSE/SSE2 codepaths on non-Intel CPUs, our assumption is that this is the specific complaint. To our knowledge this has been resolved for quite some time now.
  3. Intel paid/coerced software and hardware vendors to not support or to limit their support for AMD CPUs. This includes having vendors label their wares as Intel compatible, but not AMD compatible.
  4. False advertising. This includes hiding the compiler changes from developers, misrepresenting benchmark results (such as BAPCo Sysmark) that changed due to those compiler changes, and general misrepresentation of benchmarks as being “real world” when they are not.

The GeForce 9400M: Intel's chief competitor in the Core 2 integrated graphics market and a threatened product line


  1. Intel eliminated the future threat of NVIDIA’s chipset business by refusing to license the latest version of the DMI bus (the bus that connects the Northbridge to the Southbridge) and the QPI bus (the bus that connects Nehalem processors to the X58 Northbridge) to NVIDIA, which prevents them from offering a chipset for Nehalem-generation CPUs.
  2. Intel “created several interoperability problems” with discrete CPUs, specifically to attack GPGPU functionality. We’re actually not sure what this means, it may be a complaint based on the fact that Lynnfield only offers single PCIe x16 connection coming from the CPU, which wouldn’t be enough to fully feed two high-end GPUs.
  3. Intel has attempted to harm GPGPU functionality by developing Larrabee. This includes lying about the state of Larrabee hardware and software, and making disparaging remarks about non-Intel development tools.
  4. In bundling CPUs with IGP chipsets, Intel is selling them at below-cost to drive out competition. Given Intel’s margins, we find this one questionable. Below-cost would have to be extremely cheap.
  5. Intel priced Atom CPUs higher if they were not used with an Intel IGP chipset.
  6. All of this has enhanced Intel’s CPU monopoly.

The purpose of the suit and what would have been the associated trial would have been for the FTC to prove that Intel engaged in these actions, and more importantly that these actions were harmful to the market to a significant enough degree to run afoul of Section 5 of the FTC Act.

One other piece of more recent background information involves Dell. Dell has been under investigation by the US Securities & Exchange Commission for the past few years regarding financial irregularities. Those irregularities, as the SEC charges, were due to Intel’s secret rebates to the OEM to not use AMD processors. When Dell began using AMD processors in 2007 and those rebates stopped, Dell ceased to turn a profit.

In turn, since these payments were secret, investors had no idea that the only reason the company was profitable was due to these payments as opposed to entirely above-the-board measures by the company. The end result was that the SEC sued Dell, and last month Dell settled the case by paying a $100 million fine to the SEC. As is the case with similar settlements, the case is not legally binding proof of Intel’s actions, as Dell neither had to confirm nor deny the SEC’s charges (in essence allowing them to claim that the settlement is just the easiest way to get the SEC out of the way). It does however show us just how large Intel’s rebates to OEMs may have been.

The Settlement
Comments Locked


View All Comments

  • Ric902 - Thursday, August 5, 2010 - link

    Even today, Intel removed existing SSE2 and SSE3 optimizations from their latest high-performance IPP libraries, reverting to compiler-generated scalar code. They only optimize SSSE3 for Atom and up. Guess how massive the AMD Phenom performance drop is!
  • Pirks - Thursday, August 5, 2010 - link

    This part fucking killed me, fucking Dell, a piece of shit PC maker, I knew these fucks are shitty but didn't know the extent of their shittiness. Holy F.

    BTW spent half a day yesterday looking for 64-bit driver for my Vostro 1700 Ricoh 82c592 fucking memory stick controller, Dell fucks just don't give a shit about users upgrading to x64. Fuck.
  • justaviking - Thursday, August 5, 2010 - link

    I think you need to expand your limited vocabulary.
  • Pirks - Thursday, August 5, 2010 - link

    "Intel is under no obligation to license QPI or DMI"

    nVidia is fucked too
  • Nataku - Thursday, August 5, 2010 - link

    and... stop the swearing
  • cknobman - Thursday, August 5, 2010 - link

    I couldnt agree more. Fuck those fucking fuckers!!!

    Dell can rot in hell, never have and never will buy their overpriced and under featured pieces of sh!t.
  • Pirks - Thursday, August 5, 2010 - link

    I've been pretty happy with my Vostro 1700, the rare FULL-MATTE laptop, no fucking moronic glossy shit anywhere ever! Everything is matte! Keyboard is top notch, rivals best macbooks and vaios, and battery didn't die after 6 months like on my Alienware laptop, it's still running nice after 3 years of use, has lotsa juice, so quality wise Dell is pretty cool.

    Well... until I tried to upgrade to win7 x64, this is where Dell clowns screwed me hard. But I found all the drivers on my own and problem's solved. Screw ya Dell scumbags, you think if you don't post your fucking 64-bit drivers for older laptops I'm going to run out and buy Dell 1720 with win7 preinstalled or something now?

    How about you suck my dick again, Mikey Delley? :P Suck deep bitch, 'cause I gonna do it AGAIN when I'm about to upgrade to win8, har har har har harrrr

    I'm not gonna buy your new laptops every time I upgrade windows, eat that bitch
  • icrf - Thursday, August 5, 2010 - link

    Didn't the majority of the consumer PC market not do so well around then, too, meaning it was likely more contributory than causal?
  • Pirks - Thursday, August 5, 2010 - link

    In 2007? Are you serious?
  • IlllI - Thursday, August 5, 2010 - link

    tell us how you really feel

Log in

Don't have an account? Sign up now