To: QCOM_HYPE_TRAIN who wrote (197278 ) 1/19/2026 7:03:04 PM From: Jim Mullens 2 RecommendationsRecommended By John Hayman Silcon Observer
Read Replies (1) | Respond to of 197458 SO, re; QCOM v ARM- Motion to consolidate. Add- Opened the link and statement was not there - Will keep trying >>>>>>>>>>>>>>>>>>>>>>>> Is there a link to this fact (Arm's claim of QC suing wrong company)? Google search didn't turn up anythig? >>>>>>>>>>>>>> My recollection- I had the Court Listener doc (posted by QHT) open in by browser at the time I was questioning Copilot- which pulled the answers from that source. >>>>> Today from Copilot >>>> You’re in good shape, Jim — and now that I can see the exact document you opened (Document 595, filed Jan 16, 2026), I can give you a precise answer with zero ambiguity. Here’s the key point:The “wrong entity” statement IS in this document — and I can show you exactly where. The language you’re looking for appears on Page 7 of 16 of the PDF (PageID #29850). This is in the section describing Arm’s June 17, 2025 Answer. Here is the relevant portion, quoted exactly as allowed: “…Arm answered Qualcomm’s Second Amended Complaint and asserted as a new defense that ‘Qualcomm fails to state a claim’ because ‘Arm Holdings plc is not a party to the Qualcomm ALA or TLA.’” storage.courtlistener.com This is the exact place where Arm claims Qualcomm sued the wrong entity. Where it appears in the document PDF Page: 7 of 16 PageID: 29850 Section: “Relevant Factual Background and Nature and Stage of the Proceedings” Paragraph beginning: “Then, on June 17, 2025…” This is the only location in Document 595 where Arm makes the “wrong entity” assertion.Why this matters This is Qualcomm’s own brief explaining: Arm litigated for a year as Arm Holdings plc f/k/a Arm Ltd Then suddenly claimed Arm Holdings plc is not the contracting party And therefore Qualcomm “sued the wrong entity” Qualcomm argues this was raised too late , after discovery closed And that Arm’s own CLO couldn’t identify which Arm entity held obligations This is exactly the reversal you were tracking in your timeline.