Rambus hasn't been making many headlines lately, but that doesn't mean its crusade against the memory industry is over—quite the contrary. The litigious memory technology firm has reached a settlement agreement with Korean RAM manufacturer Hynix, which agreed to pay royalties for SDRAM products. A "proposed judgment" could also see Hynix cough up $397 million in damages.
As part of the agreement, Hynix should pay royalties of 4.25% on net sales of DDR memory sold "after January 31, 2009 and before April 18, 2010." That fee will cover not just DDR, DDR2, and DDR3 system RAM used in PCs and laptops, but also the GDDR, GDDR2, and GDDR3 varieties that typically ride shotgun with graphics processors. Oh, and Hynix has agreed to pay 1% royalties on sales of older, single-data-rate memory, as well.
This announcement comes barely a year after a jury ruled that Rambus' patent filings weren't fraudulent or anti-competitive. Rambus filed its patents while sitting on the Joint Electron Devices Engineering Council, which came up with the single- and double-data-rate SDRAM standards, then turned around and started suing JEDEC members for infringement.
Of course, this could hardly come at a worse time for Hynix. The firm is already suffering from the dreadful conditions in the memory market, and it posted net losses of 1.33 trillion won ($883 million) last quarter. Hynix says it plans to appeal the court's decision—a 1-2-year process during which it "is not required to pay the judgment."
|In the lab: FLIR's One thermal camera||39|
|Black Friday deals: Dell's U3415 curved monitor for $650 and more||30|
|Abu Dhabi government fund may be shopping GlobalFoundries||63|
|Asus goes for the gold with its 20th Anniversary GTX 980 Ti||8|
|MSI's Eco motherboards let owners fine-tune power consumption||10|
|Gigabyte's Z170X-Gaming G1 motherboard reviewed||16|
|Star Wars Battlefront video review||40|
|Club 3D active adapters convert DisplayPort 1.2 to HDMI 2.0||23|
|Phanteks' Power Splitter lets two systems run on one PSU||45|
|This is the answer to SSK's question on the Firefox news post.||+34|