More Money, Fewer Problems, No x86

NVIDIA and Intel just released their respective PR announcements a bit ago, but after much rumor mongering its official: Intel and NVIDIA are the latest duo to bury the hatchet. This comes on the heels of 3 other major Intel actions in the past two years: the EU fining Intel (which is still under appeal),

NVIDIA and Intel just released their respective PR announcements a bit ago, but after much rumor mongering it’s official: Intel and NVIDIA are the latest duo to bury the hatchet. This comes on the heels of 3 other major Intel actions in the past two years: the EU fining Intel (which is still under appeal), Intel settling with AMD (affirming GloFo as a legal venture), and Intel settling with the United Stated Federal Trade Commission.

With the exception of the EU fine that is still under appeal, this is the final outstanding major legal battle for Intel over their actions of the first decade of the 21st century. Generally speaking someone is always suing Intel – or Intel is always suing someone else – but as far as normality is concerned this is a return to normal for Intel: they’ve now settled with every significant government and corporate entity and are no longer living under a cloud of allegations from a number of parties.

So what are NVIDIA and Intel burying the hatchet over? A lot of this has to do with the same matters we saw in the FTC suit, as part of the FTC’s case was built on NVIDIA’s complaints. As you may recall the FTC didn’t get everything they wanted, and this suit looks to resolve those outstanding issues along with settling NVIDIA’s chipset allegations, and providing NVIDIA with a sizable 1.5bil compensation package for their troubles.

Background

The state of the United States patent system is such that it’s difficult if not impossible to design and build a high-tech product without infringing on someone’s patent. Snark about patent trolls aside, there are often only a handful of good methods to implement a given technology, and all of those methods are patented by someone. For these reasons there are a number of broad cross-licensing agreements in the GPU and CPU markets so that all the major manufacturers can design and build products without running afoul of another’s patent portfolio. AMD and Intel cross-license, AMD and NVIDIA cross-license, Intel and VIA cross-license, etc. Most of these cross-licensing agreements have the participants as peers, with each side getting access to the patents they need to make their agreements equal in value.

In 2004 Intel and NVIDIA went to the table, as the growing GPU market and its increasingly complex technology put Intel at risk of violating NVIDIA’s patents. This was primarily over Intel’s IGPs, which eventually would run afoul of NVIDIA’s graphics patents. In return for NVIDIA licensing the necessary patents to Intel so that Intel could continue producing chipsets with IGPs, Intel in return would license to NVIDIA their front side bus (FSB) and future buses (e.g. DMI). This is what allowed NVIDIA to enter the Intel chipset market with the nForce 4 Intel Edition chipset and to continue providing chipsets and IGPs up through the current 320M chipset.


It Seems You Can't Build One of Those, Without Licensing The Patents Behind One Of These

Although Intel and NVIDIA have never been “close” in a business sense, the modern sabre-rattling between the two doesn’t start until around 2008. At the time NVIDIA was moving forward with CUDA and G80 in order to gain a foothold in the high margin HPC market, while at the same time Intel was moving forward with their similarly parallel x86-based Larrabee project. In the FTC case we saw the fallout of this, as the FTC charged Intel with misrepresenting Larrabee and for lack of better words badmouthing NVIDIA’s GPGPU products at the same time.

As far as the Intel/NVIDIA license agreement is concerned however, it was the end of 2008 when events were set in to motion. When Intel moved from the Conroe (Core 2) architecture to Nehalem (Core iX), they dropped the AGTL+ FSB in favor of two new buses: Quick Path Interconnect (QPI) for high-end desktop CPUs and workstations/servers, and extended the existing DMI bus from a Northbridge-Southbridge interconnect to a CPU-Southbridge interconnect as Intel integrated the Northbridge on-chip. Even though DMI had been around for a while, NVIDIA had never used it before as they used their own interconnect for early 2-chip chipsets, and later went to a single chip entirely.

We don’t have access to the 2004 Intel/NVIDIA agreement, but what resulted is a dispute about just what NVIDIA’s half of the agreement covered. If you ask Intel, NVIDIA’s agreement only covers AGTL+, meaning NVIDIA would not be allowed to make chipsets for Nehalem generation CPUs. If you ask NVIDIA, Intel was playing games with the agreement’s language to lock NVIDIA out of the chipset market while still keeping the agreement in force so that Intel could continue producing IGPs.

The end result is that in early 2009 the two parties filed suit against each other. Intel’s suit asked for the courts to affirm that NVIDIA did not have rights to DMI/QPI and that NVIDIA had breached the agreement by claiming they did have rights. NVIDIA’s suit in return was filed as a response to Intel’s suit, with NVIDIA claiming that Intel’s claim had no merit and that by doing so Intel was in violation. These suits have been ongoing up until today.

The suits further branch out with the FTC’s suit. While filing their suit against Intel, NVIDIA also made formal complaints to the FTC, who was already building a cast against Intel for actions against AMD. The FTC included some of their complaints in their own suit, and when that was settled last year NVIDIA received some protections against potential Intel actions. For all practical purposes Intel is barred from making technical decisions that lock out 3rd party GPUs from their platforms for the next several years, enforced by requiring they continue to offer PCI-Express connectivity and at the same time barring Intel from making changes that would reduce GPU performance unless those changes specifically improve CPU performance.

ncG1vNJzZmivp6x7orrAp5utnZOde6S7zGiqoaenZIFyfpFooKeslaF6tLHTraOeq12strW0jKetopyZlnquu9GeZKannprGbrLEsJyrZaCnvKO4xKaqZqafYsV5gg%3D%3D

 Share!