Language Selection

English French German Italian Portuguese Spanish

'All-out war' in Intel-AMD antitrust case

Filed under
Legal

Lawyers with Intel and Advanced Micro Devices will sit down next month to discuss for the first time their latest antitrust tussle, representatives for the two companies said on Friday.

The meeting has been scheduled for the first week of August 2005. Attorneys are expected to swap names and addresses of people and documents they are likely to use at trial to defend their side of the story.

AMD filed a 48-page suit in a Delaware federal court last month, alleging that Intel uses scare tactics and coercion to prompt computer makers and other companies to use more Intel chips than ones sold by its rivals. Two days later, AMD extended its antitrust claims to include Intel's Japanese subsidiary, Intel Kabushiki Kaisha (Intel KK) by filing similar briefs with two Japanese courts.

Intel's chief executive, Paul Otellini, has said that he expects his company to come out on top in the dispute.

Intel has until Sept. 6, 2005 to file a response to AMD's complaints, court documents filed in Delaware show.

Computer retailers Best Buy and Circuit City, along with hardware manufacturers Sony, Sun Microsystems, Acer, Gateway, Lenovo, NEC-CI, Rackable and Tech Data have agreed to AMD's subpoena for information. Intel has not indicated which companies it has been in contact with.

The lawyers arguing the suits are expected to fight aggressively, according to one legal insider.

Full Story.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more