An adaptation works on a new platform but breaks compatibility with the old one. Does that lost functionality help save a patent from an obviousness challenge? In In re Netlist, Inc., Nos. 2025-1286, 2025-1296 (Fed. Cir. Nov. 13, 2026), the Federal Circuit’s answer was clearly not on this record. The appellate panel affirmed the Patent Trial and Appeal Board (PTAB) decisions finding all claims of Netlist’s two memory-module patents unpatentable as obvious.
A Memory Refresher, Without the Engineering Degree
Netlist’s memory-module patents (U.S. Patent Nos. 11,093,417 and 9,858,215) are directed to computer memory modules. Put simply, the technology at issue places buffering circuitry between memory devices and the computer’s memory controller. The specifications of the Netlist memory-module patents, which are substantively identical, describe that buffer as reducing the electrical load and improving signal integrity, while the claims also account for delay introduced by the buffer.
The dispute involved two different approaches to addressing memory. Think of two systems using different addressing conventions (not simply two brand names on interchangeable hardware). The relevant standards set forth by JEDEC, a standard-setting organization for the microelectronics industry, used chip-select signals to select groups, or ranks, of memory chips. In the alternative, the standards based on Rambus architecture identified individual chips through unique device identifiers.
The petitioners combined Perego, an earlier U.S. patent describing a buffered memory module, with a JEDEC specification for DDR2 memory (JESD79-2). The rationale was that Perego supplied the buffer teachings and JESD79-2 supplied chip-select signaling.
The Challengers Disconnected, the Controversy Stayed Live
Before addressing the merits, a procedural point deserves attention: Settling with the challengers did not eliminate Netlist’s challenge to the PTAB’s unpatentability decisions. Samsung settled and stopped participating before oral argument; Micron settled and withdrew afterward. The USPTO declined to intervene. Yet the adverse PTAB decisions remained. Netlist still had its own concrete stake in reversing them: preserving its patent claims. The panel therefore concluded that a live controversy over patentability remained.
The distinction is between settling the private dispute and undoing the agency’s decision. A dissatisfied IPR party may appeal under 35 U.S.C. § 319, and § 318(b) provides for cancellation of claims finally determined unpatentable once appellate review ends. Settlement itself does not erase that determination. Section 317(a) also distinguishes settlement before the office decides the merits from settlement afterward; even when no petitioner remains, the office may proceed to a final written decision. Finally, § 143 gives the director a right to intervene, not an obligation to do so. Here, reversal still could have provided meaningful relief to Netlist by protecting its claims from cancellation.
This is not the Federal Circuit’s first appeal to continue after a challenger stepped away. In In re Rambus, Inc., an inter partes reexamination case, Micron withdrew after oral argument, the PTO did not intervene, and the court nevertheless resolved the patent owner’s appeal because its independent appeal right and a live patentability controversy remained. In NFC Technology, LLC v. Matal, HTC settled and withdrew but the director, who had intervened, defended the IPR decision, and the court reached the merits, reversing in part and remanding.
This is not to say that every patent appeal survives settlement. Indeed, the identity of the appellant and the available relief matters. For example, in Apple Inc. v. Qualcomm Inc.., the settling petitioner (Apple) appealed decisions that had upheld the challenged claims, but the Federal Circuit found that Apple failed to establish a concrete continuing injury sufficient for Article III standing and dismissed the appeals. Netlist here occupied the opposite position: It was the patent owner seeking relief from decisions holding its own claims unpatentable. The practical lesson is that buying peace with the challengers does not, by itself, restore claims lost at the PTAB.
Breaking Rambus Compatibility Did Not Break the Reason to Combine
Netlist did not dispute on appeal that the proposed combination disclosed all of the claim limitations. Rather, its fight was over the “why”, i.e.,why a skilled artisan would be motivated to combine Perego and JESD79-2. In this vein, as it did before the PTAB, Netlist continued to argue that Perego concerned Rambus architecture and that adapting it to JEDEC would defeat its intended purpose. Netlist also argued that the modification would sacrifice backward compatibility with earlier memory devices.
While that sounds like a meaningful engineering objection, the legal question on appeal was more specific. Relying on KSR International Co. v. Teleflex Inc. and Axonics, Inc. v. Medtronic, Inc., the appellate panel explained that familiar technology can have obvious uses beyond its original purpose and clarified that the inquiry was whether a skilled artisan had an adequate reason to adapt Perego for JEDEC, not whether the adapted design would continue satisfying Rambus requirements that were not requirements of the challenged claims. Recall that the claimed invention was directed to functioning in a JEDEC-compliant architecture. Preserving Rambus compatibility, including backward compatibility with Rambus devices, was not a shared purpose of that invention. So, losing those capabilities therefore did not defeat the Perego- JESD79-2 combination advanced here.
Moreover, the appellate panel found the “why” was solidly in the record. Indeed, the PTAB had more than a collection of claim elements to work with here. It relied on Perego’s flexibility teachings, disclosures amenable to JEDEC implementations, and the dominance of JEDEC-compliant modules in the relevant market. Those technical disclosures included bussed topologies, a 64-bit data width, and row- and column-address-strobe lines. The appellate panel did not need to hold that each detail uniquely identified JEDEC architecture because collectively they undermined Netlist’s characterization of Perego as Rambus-only and supported the finding that its teachings could accommodate JEDEC. And, with respect to market evidence, Netlist’s own expert supported the finding that JEDEC-compliant modules dominated at the time of invention. Netlist did not contest that dominance or that the proposed combination was JEDEC-capable. The appellate panel thus found substantial evidence supporting the PTAB’s finding of the “why.”
However, there is one important caveat to consider: Operability is not itself a reason to combine. Indeed, showing that an adaptation can work does not explain why a skilled artisan would make it. The appellate panel addressed those questions separately, examining the PTAB’s affirmative reasons for the modification after rejecting Netlist’s intended-purpose objection.
Intended Purpose Still Has a Job to Do
To be clear, the decision does not eliminate intended-purpose arguments. In fact, it identifies circumstances in which the purpose of the earlier technology remains pertinent. First, consider the source of the asserted motivation. If a challenger relies on a reference’s own functionality to explain why an artisan would modify it, a modification that defeats that functionality can undercut the explanation.
Second, ask whether the defeated purpose is shared with the challenged invention. The appellate panel distinguished cases involving shared objectives, including vehicle stability, medical-device functionality, and high-speed polymer extrusion. A modification that defeats a purpose important to both the prior art and the challenged invention presents a different problem from losing Rambus compatibility when pursuing a JEDEC-compatible invention. To be clear, this is not necessarily a search for a particular word in a claim. The panel’s discussion of Polaris Industries, Inc. v. Arctic Cat, Inc., specifically referred to benefits described in that patent’s specification. In this aspect, the claims and disclosure should be examined together when assessing a genuinely shared purpose as opposed to assuming that an objective matters only if expressly recited.
When Does Lost Compatibility Undercut the Reason to Combine?
The panel distinguished Perego’s backward compatibility with Rambus devices from its broader teachings of upgrade flexibility and alternative configurations. That distinction identifies a useful question for future cases: Which kind of flexibility actually supplies the asserted reason to combine? If a challenger invokes a reference’s flexibility to justify a modification, a patent owner should test whether the modification preserves the particular flexibility on which that rationale depends. The question is not simply whether backward compatibility disappears, but whether its loss undermines the asserted reason for making the change. Here, the panel found adequate support for the PTAB’s decision in Perego’s teachings and JEDEC’s market dominance.
On a different record, evidence that a modification defeats the very benefit offered to justify it could give an intended-purpose argument more traction. Indeed, a potentially stronger line of inquiry for a patent owner would ask whether the proposed change defeats a genuinely shared objective, whether the asserted technical adaptation is supported, and whether the market-based reason actually connects to the claimed arrangement without hindsight. The counterarguments to this line of questioning here are substantial: Netlist did not dispute claim coverage, assert teaching away from the chip-select signals, or contest JEDEC’s dominance.
The Bottom Line: Test the Rationale, Not Just Compatibility
When trying to argue against an obviousness combination, scrutinize what the proposed combination actually loses (if anything). A lost feature matters most when it defeats the asserted reason for combining or a purpose genuinely shared with the challenged invention. “It no longer works like the original” is not a complete analysis. For businesses building products around industry standards, the lesson reaches beyond computer memory. A technical tradeoff does not defeat an obviousness challenge simply because something useful gets left behind.











