2mo ago

REPORT: Arm is sensationally canceling the license that allowed Qualcomm to make Snapdragon chips which power everything from Microsoft's Copilot+ PCs to Samsung's Galaxy smartphones and tablets

www.windowscentral.com REPORT: Arm is sensationally canceling the license that allowed Qualcomm to make Snapdragon chips, which power everything from Microsoft's Copilot+ PCs to Samsung's Galaxy smartphones and tablets (Update: Qualcomm responds)

The license cancellation could massively disrupt the Arm PC, AI, and smartphone market.

You're viewing a single thread.

207 comments

This will get RISC-V probably a big boost. Maybe this was not the smartest move for ARMs long term future. But slapping Qualcomm is always a good idea, its just such a shitty company.
- True, I just wished RISCV laptops were slightly more developed and available. As of now, the specs aren't there yet in those devices that are available. (8core@2Ghz, but only 16GB Ram, too little for me)
  Kind of a bummer, was coming up to a work laptop upgrade soon and was carefully watching the Linux support for Snapdragon X because I can't bring myself to deal with Apple shenanigans, but like the idea of performance and efficiency. The caution with which I approached it stems from my "I don't really believe a fucking thing Qualcomm Marketing says" mentality, and it seems holding off and watching was the right call. Oh well, x86 for another cycle, I guess.
  
  I think, I would go for a ARM Tuxedo PC in your position.
  Oh, still some time needed for that as well, but you can see the progress (a lot is working now at kernel 6.11)
  https://www.tuxedocomputers.com/en/Where-are-we-with-our-TUXEDO-ARM-Notebook.tuxedo
  
  ARM CPU prob means that at some point you'll get stuck with a kernel limit.
  But did you imply you would buy (now) a RISC-V laptop if it had more RAM & cores?
- You are overestimating RISC-V. It cannot save the planet alone.
  ARM provides complete chip designs.
  RISC-V is more like an API, and then you still need to design your chips behind it.
  
  I could be wrong, but I think Qualcomm designs its own chips and only licenses the "API", so it would be no difference for them.
  
  If they use Cortex cores, they are ARM designs. Oryon cores are in house based on Nuvia designs, and I assume it would still require a complete chip redesign if they decide to switch to RISC-V.
  
  From my understanding, most companies take the reference design from Arm and then alter it to fit their needs.
  
  That's a big part of what's going on. ARM is trying to move into Qualcomm's traditional business while Qualcomm is trying to move in ARM's traditional business.
  "Under Chief Executive Officer Rene Haas, Arm has shifted to offering more complete designs — ones that companies can take directly to contract manufacturers. Haas believes that his company, still majority owned by Japan’s SoftBank Group Corp., should be rewarded more for the engineering work it does. That shift encroaches on the business of Arm’s traditional customers, like Qualcomm, who use Arm’s technology in their own final chip designs.
  Meanwhile, under CEO Cristiano Amon, Qualcomm is moving away from using Arm designs and is prioritizing its own work, something that potentially makes it a less lucrative customer for Arm. He’s also expanding into new areas, most notably computing, where Arm is making its own push. But the two companies’ technologies remain intertwined, and Qualcomm isn’t yet in a position to make a clean break from Arm."
  https://www.msn.com/en-us/money/companies/arm-to-cancel-qualcomm-chip-design-license-in-escalation-of-feud/ar-AA1sK49J
  
  Interesting. So essentially Arm is butthurt that Qualcomm doesn’t want to send them a shitload of money and instead tries to do their own thing, so Arm is trying to force them into buying their product regardless?
  
  Of course i will still take RISC-V a long time to be even relevant. But in the future there could be multiple Companies that offer finished chip designs to use. As you said not every company wants and can create a design themself.
- I'll wait and see. RISC-V is a nice idea, but there are way too many different "standards" to make it a viable ecosystem.
  
  What do you mean by standards?
  
  Several differing extensions of the RISC-V core machine instructions, for example. A pain in the rear for any compiler builder.
  
  That’s a good thing, meaning you can design RISC-V CPUs without functionality you don’t need (like microcontrollers that only need basic operations). However, for those who want a complete CPU, there are RVA profiles (latest being RVA23), which are a list of extensions required to be an application-ready CPU. So there’s really just 1 “standard” for general purpose computing, everything else is for specialized products.
  
  And it does not concern you that this RVA profile is version 23? Which means there are a number of CPUs based on lower versions, too, as they don't just update on a whim? And they are incompatible, with version 23 because they lack instructions?
  So a compiler would have to support at least a certain number of those profiles (usually, parts in the embedded world are supported for 10+ years!), and be capable of supporting the one or other non-RVA extension, too, to satisfy customer needs.
  That is exactly what I meant with "too many standards".
  
  And it does not concern you that this RVA profile is version 23
  Not sure where you got that information. There are only 5 RISC-V profiles.
  And they are incompatible, with version 23 because they lack instructions?
  Like all the x86 CPUs from a few years ago that don’t have all the new extensions? Not supporting new extensions doesn’t mean the CPU is useless, only that it’s worse than new ones, as things should be when there’s progress. Or I guess you throw out your x86 CPU every time Intel/AMD create a new instruction?
  So a compiler would have to support at least a certain number of those profiles
  Do you think compilers only target one x86 version with one set of instructions? For example in x86, there’s SIMD versions SSE, SSE2, SSE3, SSSE3, SSE4, SSE4.1, SSE4.2, compilers support all of them, and that’s literally just for the SIMD instructions. What’s new?
  
  Yes, there are differences in certain x86 command sets. But they actually have a market. RISC-V is just a niche, and splintering in a small niche is making the support situation worse.
  
  making the support situation worse
  The support situation is so bad that both GCC and LLVM have extensive for RISC-V.
- Yeah, in the current macro environment Qualcomm isn't that tied down & can afford some changes (basically with a few of their biggest partners that can keep their profits up even in a few transitioning years). Not sure what prompted ARM to force such a deal instead of getting like a good compromise.
  But also fuck Qualcomm & their closed-softwareness.
  Im still hoping I can buy a RISC-V laptop (from Framework?) in 2 or 3 years & just run Linux normally.
  \ And if that can happen & RISC-V still doesn't overall prosper it's bcs of some shitty greedy deals between megacorps.

207 comments