Qualcomm wins licensing fight with Arm over chip designs

Original Article ↗ Hacker News Discussion ↗

A U.S. jury largely sided with Qualcomm in its licensing dispute with Arm over custom CPU designs, affirming that Qualcomm’s long‑standing architecture license covers its use of technology developed by acquired startup Nuvia, even as jurors deadlocked on whether Nuvia itself breached its original contract. Commenters argue that Arm’s aggressive legal stance toward a major customer, and its claim that most Arm‑compatible designs are derivative of its IP, risks chilling future architectural license deals and accelerating interest in the open RISC‑V instruction set. Many see the case as exposing weaknesses in Arm’s contract strategy and potentially undermining its ecosystem just as it faces growing competition.

Outcome and Current Status of the Case

  • Jury found that Qualcomm’s existing architecture license (ALA) covers its use of the disputed technology, giving Qualcomm a major win.
  • Jury deadlocked on whether Nuvia breached its license; that specific issue remains unresolved and could be retried, but several commenters think it is now secondary.
  • Judge reportedly said neither side had a “clear victory” overall, but the practical business win is widely seen as Qualcomm’s.

Nature of the Licensing Dispute

  • Core conflict: whether technology developed under Nuvia’s ALA could be used under Qualcomm’s older, more favorable ALA after acquisition.
  • ARM argued licenses can’t transfer on acquisition without explicit consent and even terminated both Nuvia’s and Qualcomm’s ALAs at one point.
  • Qualcomm’s position: it already had a broad “modify” ALA, did not transfer Nuvia’s license, and either rebuilt designs from scratch or kept Nuvia tech within the scope of its own ALA.
  • ARM also pushed a strong “derivative work” theory: that ARM-compliant CPU designs and RTL are derivatives of the ARM ISA, alarming many architectural licensees.

ARM’s Strategy and Perceived Self‑Harm

  • Many see ARM’s suit against a long‑time, high‑paying customer as a strategic blunder that damages trust.
  • Motive is viewed less as short‑term money and more as long‑term control over licensees and extraction of higher royalties, especially when customers replace ARM-designed cores with their own.
  • Several predict this will chill startups building custom ARM cores and complicate acquisitions, pushing new designs toward alternative ISAs.

RISC‑V as Alternative

  • Repeated theme: ARM’s behavior is a major advertisement for RISC‑V’s open ISA and a reason for big players to hedge away from ARM before future licensing conflicts.
  • Others counter that RISC‑V is not yet competitive in Qualcomm’s performance segment and is still far from “prime time” for consumer and server CPUs.
  • Some argue there is already high‑performance RISC‑V IP available for licensing and that upcoming server parts may close the gap.

Technical / ISA and IP Issues

  • Debate over whether an ISA vendor can reasonably claim that all compliant implementations are derivative works, and what that implies for RTL and compilers.
  • ARM’s stance here is seen by many as overreach that threatens all ALA holders.
  • Discussion touches on RISC‑V extensions (bitmanip, vectors, RVA22/RVA23) and whether the ISA design itself limits future competitiveness.

Software Ecosystem and Adoption

  • Multiple comments stress that hardware performance is only a small part; ecosystem, compilers, and mass-market devices drive real adoption.
  • ARM’s eventual success on desktop and server is credited partly to Apple’s ARM Macs catalyzing software work; RISC‑V currently lacks a comparable catalyst.
  • For embedded use, switching ISAs is seen as easier; for general‑purpose computing, the transition cost and QA burden remain major barriers.