Slashdot Mirror
Intel: Steer Clear Of Our Patents (axios.com)
An anonymous reader writes: Intel posted a long blog post yesterday touting the success and evolution of its 40-year-old x86 microprocessor -- the one that powered the first IBM personal computer in 1978 and still powers the majority of PCs and laptops. But it wasn't just a stroll down memory lane. Intel ended the post with a reminder that it won't tolerate infringement on its portfolio of patents, including those surrounding x86. The company wrote, "Intel invests enormous resources to advance its dynamic x86 ISA, and therefore Intel must protect these investments with a strong patent portfolio and other intellectual property rights. [...] Intel carefully protects its x86 innovations, and we do not widely license others to use them. Over the past 30 years, Intel has vigilantly enforced its intellectual property rights against infringement by third-party microprocessors. [...] Only time will tell if new attempts to emulate Intel's x86 ISA will meet a different fate. Intel welcomes lawful competition, and we are confident that Intel's microprocessors, which have been specifically optimized to implement Intel's x86 ISA for almost four decades, will deliver amazing experiences, consistency across applications, and a full breadth of consumer offerings, full manageability and IT integration for the enterprise. However, we do not welcome unlawful infringement of our patents, and we fully expect other companies to continue to respect Intel's intellectual property rights. Also read: Intel Fires Warning Shot At Qualcomm and Microsoft Over Windows 10 ARM Emulation.
Then I guess we can now consider the x86 and x86-64 instruction sets subject to what Richard Stallman has referred to as the Java Trap. A free program with proprietary dependencies is trapped, and Intel is asserting that the x86 and x86-64 instruction sets are proprietary.
Intel never hauled AMD to court for AM64. At the time, Intel was hoping to break clean of x86 by introducing the Itanium, while AMD took the tack of extending the x86 instruction set to 64-bit, something that Intel desperately wanted to avoid. In short, Intel tried to shut AMD out of the market the innovative, rather than the legal way: it just happened that VLIW, or EPIC, was such a bust that even Linux hated it, while AMD scored a coup in the market.
After that, Intel tried coming up w/ their own 64-bit extension to the x86, but Microsoft, which by then had already sunk effort into making 64-bit versions of Windows XP based on AMD, made it clear to Intel that they were not gonna support 2 different x86 instruction sets. This was similar to what Microsoft had done in the past, when they forced AMD, Cyrix, Centaur and Winchip to agree on multimedia extensions. Once Intel got this message, they realized that the only clean way of doing this was doing a cross licensing agreement w/ AMD. There are a couple of instructions in the Intel-64 instruction set that are a tad different from AMD64, but otherwise, they are identical.
At any rate, the biggest thing Intel demonstrated was that having sheer expertise at fabs and manufacturing capacity beat the crap out of any inherent architectural superiority any competitor might have: that's how they felled every RISC rival that they had. Like the Alpha & the PA-RISC was way superior to them, but once they could pack 2 or more cores in a package, along w/ the Windows NT kernel being the unified basis of all Windows OSs, it was easy to catch up w/ them from a stance of price points. Intel doesn't have to sue anybody to preserve x86: worst case, they could simply start manufacturing Snapdragons or A10s or whatever, and horn in on the action