What the FTC Didn’t Get

Going in to this suit, the FTC asked for a number of things, and while they got many of those things in the settlement they didn’t get all of them.  The following is our list of things the FTC asked for from our earlier article, and whether they got that item under the terms of the settlement or not.

FTC/Intel Lawsuit Requested Remedies
Request Result
For Intel to be barred from paying OEMs to not use AMD processors Intel is barred from offering rebates, kickbacks and some forms of volume discounts
For Intel to be barred from threatening OEMs in to not using AMD processors Intel is barred from witholding advertising money, technical support, or chips from OEMs using AMD CPUs
For Intel to be barred from selling products below cost Intel is not allowed to sell CPUs or chipsets below the product cost
For Intel to be barred from designing or selling products that inhibit 3rd party GPU performance Intel is not allowed to make design choices that reduce GPU performance unless they can prove doing so improves CPU performance
For Intel to make reparations to customers who used their compiler not knowing that it may discriminate against non-Intel CPUs Intel is required to set up a $10 million fund to pay for customers who were mislead and wish to switch to another compiler
For Intel to to be barred from making misleading statements about their compiler and its performance Intel is required to disclose that their compiler may discriminate against non-Intel CPUs, and is not allowed to claim that their compiler is faster for non-Intel CPUs when it is not
For Intel to license the QPI and DMI buses to third party chipset manufacturers. The FTC did not get this; Intel is under no obligation to license QPI or DMI
For Intel to allow AMD and Via to outsource their x86 CPU fabrication to third party fabs Intel is required to allow AMD and Via to outsource their x86 CPU production to third party fabs so long as those fabs uphold certain IP protection requirements
For Intel to stop badmouthing competing products unless they have solid scientific evidence (primarily in the GPU space) Compilers: Yes
GPUs: No
For Intel to pay for the independent organization (Technical Consultants) that will monitor their compliance Intel is required to pay up to $2 million over 10 years for the Technical Consultants to monitor their compliance

The FTC got the vast majority of what they requested. Intel is barred from engaging in a number of anti-competitive practices, including benefits for OEMs to only use Intel CPUs, punishments for OEMs using non-Intel CPUs, from designing products to reduce GPU performance, from outright denying the transfer of an x86 license should a current holder be purchased, and from making misleading statements about their compiler.

In fact there’s really only two things on the FTC’s list that they didn’t get: they didn’t get chipset licenses, and they didn’t get stronger protections for AMD and NVIDIA’s GPU divisions.  It’s probably not a coincidence that both of these issues were primarily of importance for NVIDIA, as AMD does not make Intel chipsets and AMD is not currently locking horns with Intel over high performance computing using GPUs. For as much as the FTC got out of this settlement, it’s interesting that they did not get these last two items. It may very well be that NVIDIA has truly given up on making a DMI/QPI chipset, in which case the chipset requests would be rendered moot. But NVIDIA has claimed loudly to the FTC that Intel is hurting their business by making false claims about CPU and Larrabee performance versus GPGPU performance, and there’s nothing in this settlement about that.

It’s worth noting that NVIDIA did not release an official response to this settlement even though it has directly impacted them. There are a number of ways to interpret this, but the most likely interpretation is that the two companies are going to continue butting heads unabated. AMD and Intel may have peace, but right now it’s a safe bet that NVIDIA and Intel do not.

Final Thoughts

Wrapping things up, we’ve looked at what the FTC’s complaints were, what they asked for, and what they’re getting out of this settlement. What remains however is probably the most important question for computer buyers reading this article: how will it impact you?

The short answer is that it won’t. Computers won’t become cheaper, new Intel-compatible chipsets won’t be introduced, the forthcoming fusion of the CPU won’t be changing schedule, etc. In reality most of the things Intel is being barred from doing are things that they discontinued doing long ago if they did them at all (note that this settlement is not an admission of guilt on Intel’s part). The FTC calls these measures corrective, but outside of the compiler requirements these measures would better be described as preventative. This settlement is structured as a list of things Intel can and can’t do, and almost all of the measures are things they already have or have not been doing.

The most unexpected measure to come out of this settlement is without a doubt the “change of control” requirements. This opens the door to another company taking over one of the two non-Intel x86 licenses from either AMD or Via by buying them out, but this is by no means a given. It’s something worth keeping an eye on for now, but it doesn’t appear to be something that is going to be acted upon any time soon.

The biggest impact from this settlement will be what does not happen, and that’s a repeat of the Athlon 64/Pentium 4 situation in 2003, with Intel using their marketing muscle and underhanded tactics to limit AMD’s progress at a time where they offered a superior CPU. Now that Intel has already been through this process and the FTC will be regularly monitoring their compliance, any kind of underhanded tactics against AMD would quickly get them in trouble with the FTC with little recourse to get out of it. In spite of the corrective nature of the settlement it probably doesn’t go far enough to completely undo the damage that AMD suffered if all of the FTC’s claims are true, but between this settlement and the private AMD settlement quite a lot of requirements have been hoisted onto Intel.

Ultimately, is this enough to prevent anti-competitive abuse in the future? The most optimistic response is that hopefully we never find out the answer to that.

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