Language Selection

English French German Italian Portuguese Spanish

AMD's battle with Intel to go West?

Filed under
Legal

AMD vs Intel AMD's legal action against Intel in the US District Court of Delaware could up stumps and move to the US District of Northern California, if plaintiffs already engaged in proceedings against Intel have their way, court documents seen by The Register reveal.

The Delaware Court was this week notified that two Northern California plaintiffs, Michael Brauch and Andrew Meimes, have requested the Judicial Panel on Multidistrict Litigation (JPML) order the transfer of four cases coming up before the Delaware Court to be transferred to Northern California and consolidate them and ten anti-Intel class actions already taking place there.

Among those four Delaware cases is AMD vs Intel and Intel KK - the latter is Intel's Japanese subsidiary. The others are all cases filed on 6 and 8 July 2005.

The ten Northern California were all filed after AMD's 27 June 2005 complaint, suggesting they, like the three extra Delaware cases, were filed in response to AMD's lead. The ten Northern California cases list "consumers who purchased Intel microprocessor computer chips" as plaintiffs - as do the three additional Delaware cases.

According to the JPML request, all the extra cases "arise out of the same or similar illegal antitrust conduct and allege substantially similar claims... [and] a common core of factual allegations, namely, that Intel illegally maintained its monopoly power in the relevant microprocessor market and/or engaged in a combination and conspiracy to suppress and eliminate competition in that market by fixing the prices and/or allocating markets for Intel chips solid in the United States and elsewhere, thus overcharging Original Equipment Manufacturer purchasers and consumers for prices paid for Intel chips during the relevant time period".

The request notes that none of the cases have heard responses from Intel, and that combining them would save considerable court time and costs. Why move to Northern California rather than Delaware? Because that Court has the majority of cases already.

No date was given for a decision on the motion to transfer. The JPML meets every two months. Its next convention takes place next week, on 28 July, where it will consider a host of motions to transfer, but not MDL-1707, the request concerning the AMD case and others. That means the request will not be heard until late September at the earliest, by which time Intel should have filed its response to AMD's complaint.

Full Story.

More in Tux Machines

Mozilla: Code of Conduct, Kelly Davis, Celebrate Firefox Internet Champions

  • ow We’re Making Code of Conduct Enforcement Real — and Scaling it
    This is the first line of our Community Participation Guidelines — and an nudge to keep empathy at center when designing response processes. Who are you designing for? Who is impacted? What are their needs, expectations, dependencies, potential bias and limitations?
  • Role Models in AI: Kelly Davis
    Meet Kelly Davis, the Manager/Technical Lead of the machine learning group at Mozilla. His work at Mozilla includes developing an open speech recognition system with projects like Common Voice and Deep Speech (which you can help contribute to). Beyond his passion for physics and machine learning, read on to learn about how he envisions the future of AI, and advice he offers to young people looking to enter the field.
  • Celebrate Firefox Internet Champions
    While the world celebrates athletic excellence, we’re taking a moment to share some of the amazing Internet champions that help build, support and share Firefox.

Canonical Ubuntu 2017 milestones, a year in the rulebook

So has Canonical been breaking rules with Ubuntu is 2017, or has it in been writing its own rulebook? Back in April we saw an AWS-tuned kernel of Ubuntu launched, the move to cloud is unstoppable, clearly. We also saw Ubuntu version 17.04 released, with Unity 7 as the default desktop environment. This release included optimisations for environments with low powered graphics hardware. Read more Also: Ubuntu will let upgraders ‘opt-in’ to data collection in 18.04

The npm Bug

  • ​Show-stopping bug appears in npm Node.js package manager
    Are you a developer who uses npm as the package manager for your JavaScript or Node.js code? If so, do not -- I repeat do not -- upgrade to npm 5.7.0. Nothing good can come of it. As one user reported, "This destroyed 3 production servers after a single deploy!" So, what happened here? According to the npm GitHub bug report, "By running sudo npm under a non-root user (root users do not have the same effect), filesystem permissions are being heavily modified. For example, if I run sudo npm --help or sudo npm update -g, both commands cause my filesystem to change ownership of directories such as /etc, /usr, /boot, and other directories needed for running the system. It appears that the ownership is recursively changed to the user currently running npm."
  • Botched npm Update Crashes Linux Systems, Forces Users to Reinstall
    A bug in npm (Node Package Manager), the most widely used JavaScript package manager, will change ownership of crucial Linux system folders, such as /etc, /usr, /boot. Changing ownership of these files either crashes the system, various local apps, or prevents the system from booting, according to reports from users who installed npm v5.7.0. —the buggy npm update.

Windows 10 WSL vs. Linux Performance For Early 2018

Back in December was our most recent round of Windows Subsystem for Linux benchmarking with Windows 10 while since then both Linux and Windows have received new stable updates, most notably for mitigating the Spectre and Meltdown CPU vulnerabilities. For your viewing pleasure today are some fresh benchmarks looking at the Windows 10 WSL performance against Linux using the latest updates as of this week while also running some comparison tests too against Docker on Windows and Oracle VM VirtualBox. Read more