AMD and Intel have had their differences. And by differences, we mean Intel engaging in anti-competitive actions that they’ve been found guilty of in the European Union.

But all of this was supposed to come to a close last month, when AMD and Intel buried the hatchet and made up for past offenses. In return for some cash, some good behavior out of Intel, and for Intel to stop trying to block the Global Foundries deal, AMD would drop all of their civil and regulatory complaints against Intel. And that would be the end of Intel’s legal problems with various governments, right? No, as it turns out that’s wrong.

The catalyst for Intel’s legal woes (besides their own actions, obviously) has been AMD complaining to various regulatory boards about anti-competitive actions undertaken by Intel. Based on those complaints, the European Commission, the South Korean FTC, and the American FTC have been investigating Intel for some time now over these alleged actions. Intel has been found guilty and fined in the EU and South Korea (with both cases on appeal) while the American FTC has continued to investigate.

In fact despite the FTC just now suing Intel, this is actually about half-way through the process. The FTC investigation is done, and they have been negotiating with Intel in private for quite some time to get the matter settled. A lawsuit is the next step for the FTC, when those negotiations break down. Those negotiations have in fact broken down, so here we are: the FTC has sued Intel, and the biggest court battle ever for Intel is soon to begin.

What the FTC Accuses Intel of Doing in the CPU Market

As the FTC’s investigation into the matter is already over, they have published a complete list of complaints against Intel which will be the basis of the coming trial. Based on these complaints the FTC case is a significant departure from the EU and South Korean cases, as the FTC is accusing Intel over not only anti-AMD shenanigans early this decade, but of continuing anti-AMD and anti-NVIDIA shenanigans right up to this day.


The Athlon, the processor that's at the root of all of Intel's legal troubles

The case fundamentally breaks down into two halves: what Intel did against AMD in the CPU market, and what they’re continuing to do against AMD and NVIDIA in the GPU market. Let’s start with the CPU-focused complaints:

  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 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.

Interestingly enough, the FTC cites Intel’s reasoning for all of this being that the company was at a competitive disadvantage, and engaged in these actions to buy time to improve their products. The timelines given place specific emphasis on the Athlon (K7) launch in 1999, and the Athlon 64 (K8) launch in 2003. This is a somewhat different take than in past cases, where Intel was merely accused of attempting to keep AMD’s overall market share down rather than specifically bridging performance gaps.

The FTC believes that the effects of all of these actions have (besides limiting AMD): served to drive up CPU prices, driven up CPU distribution costs, limited CPU innovation, harmed AMD’s ability to market CPUs, limited the ability of OEMs to innovate and differentiate their products, and reduced the quality of industry benchmarking.

Ultimately all of the CPU accusations are for things long past; none of the FTC’s CPU-related allegations are for things that have occurred in the last few years. We would not take this as a sign that the FTC is happy with the current market situation, but that they have no proof that they wish to follow up on that would show Intel as having engaged in anti-competitive actions in the CPU market in the last few years. The FTC does want some significant changes at Intel, which we’ll discuss in a bit.

Finally, there’s also the matter of AMD. Since AMD and Intel have settled their matters, AMD is presumably not going to participate in these proceedings as an ally of the FTC. As the FTC is going ahead on these charges, it’s clear that they aren’t worried about what this means for their position.

What the FTC Accuses Intel of Doing in the GPU Market

When we were first reading the FTC’s suit, the thing that caught us entirely off-guard was that it wasn’t merely about anti-competitive actions in the CPU market, but anti-competitive actions in the GPU market as well. While the CPU-related accusations are all for things done well in the past, the GPU accusations are fresh, very fresh. These run right up to today, and include the Larrabee project and the anti-competitive actions Intel has taken in the GPU market both outside and inside that project. To get right to the point, the FTC believes that as things currently stand, Intel is likely to get a monopoly on the GPU market similar to the one that they have on the CPU market, and that this monopoly will be created by abusing their CPU monopoly.

In the complaints about the GPU market, both NVIDIA and AMD are mentioned as being the primary competitors for Intel. The bulk of the complaints however are related to NVIDIA and their chipset business, as while AMD stands to be harmed too by an Intel GPU monopoly, it’s NVIDIA that stands to be the most harmed. In effect Intel has finally gotten AMD off their back for CPU matters, only to now have NVIDIA on their back for GPU matters.


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

Just to note where things stand, the FTC already estimates that Intel has approximately 50% of the GPU market. This is consistent with the vast number of Intel IGP-equipped computers that are on the market. Depending on how you intend to count various user bases, this stands to grow in the future as Intel puts their IGP GPUs first on-chip, and then on-die with their CPUs.

The basis of the FTC’s complaint here is that they believe Intel is threatened by the rise of GPUs as programmable computing devices, and that using them in GPGPU situations threatens Intel by making CPUs less important (something NVIDIA has been trying to play for ages) and as a result less profitable. The FTC argues that Intel is seeking to establish a monopoly here to maintain their overall control of (and high margins in) the computing market.

As for the specific complaints:

  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 2 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 FTC believes that all of this will help Intel to establish a GPU monopoly. This is on top of all other effects of Intel’s actions, which are similar to the effects of their actions in the CPU market: driving up GPU prices, driving up GPU distribution costs, limited OEM differentiation, and limited GPU innovation.

There’s also one last complaint unrelated to GPUs, which has to do with standards.

  1. Intel used their market position to delay AMD and NVIDIA’s implementations of USB and HDCP by refusing to make the specifications accessible until Intel’s products were ready. We know that there has been some strife among Intel and virtually everyone else over Intel dragging its heels on the USB3 specification, but it’s not clear if this complaint is about that.
Intel's Response & What The FTC Wants
Comments Locked

114 Comments

View All Comments

  • yuhong - Wednesday, December 16, 2009 - link

    "This CPU GPU convergence is a convenient excuse for Intel to force "bundle" its crappy graphics with its CPU. "
    And to be honest, AMD will be doing the same thing later in 2011 with Fusion, and of course the graphics will be better.
  • prodystopian - Wednesday, December 16, 2009 - link

    "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 the specific complaint. To our knowledge this has been resolved for quite some time now."

    Can someone explain this? What compiler that Intel designs would an AMD CPU have to run? Does AMD not make their own compiler?
  • Ryan Smith - Wednesday, December 16, 2009 - link

    There are a number of x86 C/C++ compilers out there. The 3 most popular ones are the GCC compiler (free and open source), the Microsoft Visual Studio compiler, and the Intel C++ compiler. The Intel compiler in particular is rather popular as Intel has proven to be quite adept at extracting meaningful SSE optimizations out of code, and hence it's used in a lot of performance-critical situations. AMD does not make their own compiler (it's very, very hard work) but they do contribute to the GCC compiler.

    When a compiler is using advanced code and wants to generate a binary that is backwards compatible, it will create multiple codepaths, with the program itself deciding which one to use depending on what feature set the codepath needs versus what the current CPU offers. For a time, Intel's compiler was simply checking for Intel processors, and ignoring AMD processors regardless of the feature set. As a result programs compiled with the Intel compiler would not take SSE/SSE2 codepaths on AMD processors, even if the processor did support that feature.
  • JumpingJack - Thursday, December 17, 2009 - link

    Ironically, one example is Lame MP3 compilations -- the Intel compiler compiles better code for an AMD CPU than does the MS compiler.
  • prodystopian - Wednesday, December 16, 2009 - link

    Thank you very much. I am familiar with GCC and VS but didn't know Intel had their own C++ compiler.
  • ltcommanderdata - Wednesday, December 16, 2009 - link

    Could Intel argue that they didn't want to spend time verifying and supporting the functionality of the SSE/SSE2 code path on AMD processors and so disabled it? To avoid liability if something did go wrong and say data got corrupted. Or can it be assumed the AMD's SSE/SSE2 implementation is 100% compatible with that of Intel's implementation with no need to verify compiler compatibility?
  • Ryan Smith - Wednesday, December 16, 2009 - link

    It can be assumed that AMD's SSE/SSE2 implementation is 100% compatible. There was no technical reason to take a different codepath on any processor that identified itself as SSE2-capable.
  • jensend - Wednesday, December 16, 2009 - link

    The most crucial part of all of this is the demand that Intel license QPI and DMI. Ever since coming out with the Pentium M and Centrino Intel has been doing a lot of odd things to crush the 3rd-party chipset market.
  • DigitalFreak - Wednesday, December 16, 2009 - link

    Hell no. If Nvidia gets a DMI / QPI license, there goes SLI on Intel chipsets. Besides, Nvidia chipsets are buggy as hell.
  • jensend - Thursday, December 17, 2009 - link

    Intel would be perfectly within its rights to make the continuation of the SLI licensing agreements a condition for their licensing QPI to nVidia. I can't imagine the FTC having a problem with that; that's just sound business.

    Don't know where you're getting your beef with nV chipsets from. nV and VIA showed years ago that they have the resources to do just as well with chipsets as Intel and AMD, but they've been squeezed out by anticompetitive practices. The death of the third-party chipset market is really bad news for consumers.

Log in

Don't have an account? Sign up now