Language Selection

English French German Italian Portuguese Spanish

Rambus names Samsung in antitrust lawsuit

Filed under
Hardware

Rambus has added Samsung Electronics to its antitrust lawsuit against most of the DRAM industry, another development in the souring of relations between the two former partners.

Rambus' antitrust lawsuit, filed last May against Infineon Technologies, Hynix Semiconductor, Micron Technology and Siemens, alleges that those companies conspired about five years ago to keep the RDRAM (Rambus dynamic RAM) design from competing with their own SDRAM (synchronous dynamic RAM) chips by underproducing the RDRAM chips and creating an undersupply that would keep prices high.

Infineon and Hynix have already pleaded guilty to corporate price-fixing charges as part of an investigation by the U.S. Department of Justice. Executives from Infineon and Micron have also entered guilty pleas and spent time in prison.

Rambus has since removed Infineon and Siemens from the antitrust case as part of a broader settlement of legal disputes between those companies. But Samsung, the world's largest DRAM manufacturer, has now been lumped in with the rest of the accused companies, Rambus said in a filing with the U.S. Securities and Exchange Commission on Wednesday.

The antitrust case is a separate legal battle from the long-running dispute over whether companies that make SDRAM chips are infringing upon patents held by Rambus. When the first patent infringement lawsuits were filed by Rambus in 2000, Infineon, Hynix, and Micron challenged the validity of Rambus' patents. But Samsung chose instead to sign a license to those patents, a huge boost for Rambus at the time.

The dispute is still ongoing between Rambus, Hynix and Micron. Rambus and Infineon agreed earlier this year to settle all outstanding litigation between the two companies, including the antitrust lawsuit, as part of a licensing agreement.

Full Story.

More in Tux Machines

today's leftovers

'Turbo Boost Max 3.0' and Mesa 17.2.4

  • Turbo Boost Max 3.0 Support For Skylake Fixed With Linux 4.15
    The platform-drivers-x86 updates have been sent in for Linux 4.15 and include a range of improvements for Intel hardware support. One of the bigger items is support for Skylake CPUs with Turbo Boost Max 3.0.
  • Mesa 17.2.4 Graphics Stack Lands for Ubuntu 16.04 LTS and Ubuntu 17.10 Gamers
    Canonical's Timo Aaltonen reports on the availability of the Mesa 17.2.4 open-source graphics drivers stack on the X-SWAT updates PPA for Ubuntu 16.04 LTS and Ubuntu 17.10 systems. Ubuntu systems have always lagged behind the development of the Mesa 3D Graphics Library, the Linux graphics stack containing open-source drivers for Intel, AMD Radeon, and Nvidia GPUs, but they usually catch up with it through a specially crafted PPA (Personal Package Archive) repository that can be easily installed by users.

OSS Leftovers

  • The Future of Marketing Technology Is Headed for an Open-Source Revolution
  • Edging Closer – ODS Sydney
    Despite the fact that OpenStack’s mission statement has not fundamentally changed since the inception of the project in 2010, we have found many different interpretations of the technology through the years. One of them was that OpenStack would be an all-inclusive anything-as-a-service, in a striking parallel to the many different definitions the “cloud” assumed at the time. At the OpenStack Developer Summit in Sydney, we found a project that is returning to its roots: scalable Infrastructure-as-a-Service. It turns out, that resonates well with its user base.
  • Firefox Quantum Now Available on openSUSE Tumbleweed, Linux 4.14 Coming Soon
    Users of the openSUSE Tumbleweed rolling operating system can now update their computers to the latest and greatest Firefox Quantum web browser.
  • Short Delay with WordPress 4.9
    You may have heard WordPress 4.9 is out. While this seems a good improvement over 4.8, it has a new editor that uses codemirror.  So what’s the problem? Well, inside codemirror is jshint and this has that idiotic no evil license. I think this was added in by WordPress, not codemirror itself. So basically WordPress 4.9 has a file, or actually a tiny part of a file that is non-free.  I’ll now have to delay the update of WordPress to hack that piece out, which probably means removing the javascript linter. Not ideal but that’s the way things go.

Red Hat and Fedora Leftovers