If anybody in Qualcomm leadership is reading this thread: this is a good start, and I applaud you for it. There is also a lot more to do if you're serious about growing your market penetration beyond phones.
The drivers might be up on LKML, but they're not mainlined yet. And this is just gen5. It would be great if you could fix your gen4 and 4.5 drivers, so that people building products with your chips weren't stuck on an orphaned vendor kernel that doesn't even upstream to your public fork.
Also your boot-chain is still closed and proprietary, and completely different than the one used by all other ARM vendors. Being the special snowflake is not helping your business or your customers.
And don't even get me started on Gunyah and GearVM, or on the proprietary, locked nature of your BSP, or how far behind TI and NXP you are on software quality and ease of use. Maybe also consider releasing some actual documentation on your chips.
I know multiple developers who have sworn off Qualcomm and will never design with your chips again at any price point. Your closed-off support model is 100% the culprit, and it hurts your core business. Any software support revenue that you managage to extract comes at the cost of goodwill and future chip sales.
Your chips are good - best in the industry. If you can up your software game to match, you'll really meet your potential.
> Also your boot-chain is still closed and proprietary
Nowadays the entire thing until you land in EL1 needs to be signed by Qualcomm as well. This is without "Secure Boot" enabled. OEMs only get to run code under the hypervisor. And you might want to use a part of the hardware but someone decided the VM your code runs in shouldn't have access to that, too bad.
> ... Also your boot-chain is still closed and proprietary, and completely different than the one used by all other ARM vendors. Being the special snowflake is not helping your business or your customers. ...
Why does the boot-chain matter? Can't we just have a custom U-Boot implementation that interacts with the bespoke boot chain while providing standard UEFI support to the rest of the system? Isn't that how Asahi works?
It matters when you're doing custom hardware, or when you're designing a product where boot speed matters, or when you need to implement something special.
A full-featured U-Boot implementation would be fine IMO. But for the generations that I've used, that's not on the table. What we get is a proprietary flow through a proprietary hypervisor into a fork of Android's bootloader (even if vanilla Linux is the target OS). There's no way to control startup boot options, and no way to use KVM, Xen or any hypervisor except the proprietary one that's also part of the boot chain.
This doesn't lend itself to flexible products, or to products that are easy for a company to design or support. That is why things like this happen: https://news.ycombinator.com/item?id=46008156
Aside from the sibling comments, it also matters that you need to be able to review it if you need to build a truly "secure" product. History is littered with broken, unfixable secure boot implementations.
Because a computer isn't just a processor. It has to interact with an EC, IO controllers, and whatnot, and if you don't have control over the boot chain, all of that stuff becomes an even bigger PITA than it already is.
Awesome, that's great to hear. Now if Qualcomm would only relax the walls between their business units, their other customers could benefit as well.
Who benefits from having separate BUs maintain fully separate software stacks? It's duplicated, wasted effort on Qualcomm's part. Maybe it lets them double-charge their customers for this duplicate effort, but that feels short-sighted. It leaves a bad taste in their customers' mouths. And there's certainly no benefit in delivered software quality.
Qualcomm should be making it easy for everybody to buy and use their chips, not artificially segmenting every single customer. They could sweep the market so hard if they were just a little less greedy.
If I was to guess, id say someone did this as a side project at QC because maybe they like FOSS and want to give something back. Given the partnership between QC and MSFT for laptops and Google for android, I won't be surprised if we never see interest from QC for any real linux hardware.
In particular, the long battery runtimes – usually one of the strong arguments for ARM devices – were not achieved under Linux.
A viable approach for BIOS updates under Linux is also missing at this stage, as is fan control.
Virtualization with KVM is not foreseeable on our model, nor are the high USB4 transfer rates.
Video hardware decoding is technically possible, but most applications lack the necessary support.
There is nothing in this press release to suggest they've changed.
White label reseller isn't really the right term. They don't design most of their components and buy them wholesale, but they do assemble them and most relevant to this particular comment thread, they do a lot of the device firmware and support stuff.
It's exactly the stuff that they actually do themselves that Qualcomm has been making very hard.
As someone who uses Mobile Linux, I am pretty excited to see this, but I can't help but wonder if this is only a "Business decision" and not necessarily Qualcomm turning over a new leaf for being FOSS friendly:
I'm personally rooting for "business decision" over "turning over a new leaf".
If FOSS support is motivated by a clear profit motive, then it'll be viewed positively by shareholders and stick around no matter who is in charge. If FOSS support comes from "turning over a new leaf", it could be dropped at a moment's notice in response to a leadership change.
IMO we will always see far better FOSS support from the private sector when the time they invest has a positive ROI that is obvious and easy to brag about in a quarterly earnings call.
Incentives trump feelings for publicly traded companies 99 times out of 100. People constantly anthropomorphize them, but they aren't people (regardless of similarities in the law), and they definitely don't act like people, at least normal ones. At best, you can view them as something like a sociopath. I wouldn't look at a sociopath acting nicer and think "oh, they turned over a new leaf" because they aren't just going to change how their mind works, I'd think "oh, they found a reason to act in a way I like for the time being. I hope it isn't short lived."
Snapdragon does poorly I think because it's a bet if it works or not. Windows runs things seamlessly other than OpenGL (it can run that too but it's not anything strait forward - needs the gl to dx store app thing) but the other reason is cost. for the premium business laptop most buyers (business) won't budge off Intel even because of the "no one got fired for buying IBM" mentality at the big Enterprises Ive been at.
I will say with my 8 gen 3 snapdragon I'm impressed and also disappointed - stupid thing needs active cooling and I'm pretty sure it's bad enough that it's desoldered or damaged the core or something from heat but also you can't get driver updates for the GPU if you wanted because Qualcomm be the way it do.
Driver update depends on your OEM. Both ARM and Qualcomm send driver updates for their premium and upper highend Socs. The support reaching your phone is on the OEM. Google has started to push direct GPU driver updates starting with Pixel 10. So, hopefully others may follow too.
I've used basically every Windows on Arm machine - I actually quite like my X Elite ThinkPad T14s Gen6, compared the the X13s - feels like they got everything right, that the X13s got wrong
Of course it's a "business decision". Companies don't do things for any other reason. They see a benefit to upstreaming in this instance, and will do it again (or not) depending on whether or not they expect to see benefits in the future.
This is no different from any other company that has "embraced" open source.
I'd imagine it's purely because not doing it turned out to be PITA in the long term.
As with pretty much all other ARM cpu vendors that pushed for their own kernel fork just to have drivers that did not need to be okayed by mainstream kernel, it was faster iteration to deliver something working to their clients; but it was also PITA to their clients, especially when industry started demanding longer support for their devices
It'll probably be as much of a second class citizen elsewhere (the real problem is the hardware hasn't as good as Apple Silicon laptops but has been in the same price class at the bottom) but it's good they chase everywhere rather than just one use case.
In the case of Linux, that issue is solely because of non-upstreamed drivers. With that, it can be a first class citizen just like any other processor.
Their problem was that they had the performance claims and marketing of Apple but the implementation of Microsoft Teams. Apple M1 was shaky but all the groundwork was there and it took off. Qualcomm was highly questionable at best.
Software-wise: Ubuntu Touch, PostmarketOS, and Mobian are all actively maintained. Ubuntu Touch uses Lomiri as its UI which is somewhat bespoke (though they're working on disentangling it from the distro for packaging elsewhere), the others use various mobile Linux UIs (and there's a surprisingly large variety of options there).
> Their Snapdragon X laptop didn't do very well, and they likely realize an ARM Windows laptop will always be a second class citizen
Why? So far ARM laptops provide either vastly better battery life for the same performance or vastly better performance for the same battery life. Even versus discrete GPUs.
Within a couple years from now you're gonna look like an utter fool for buying x86 (and Nvidia / AMD / Intel GPU) unless Intel, AMD and Nvidia really pull their head out of the sand.
There's a few specific workloads like local LLM and legacy where you'd want a discrete GPU or x86, but otherwise it is looking like GG.
I hope this is motivated by shrewd decision-making in response to market pressure, as opposed to being strictly a perception thing.
While it would be great for Qualcomm to "do the right thing" in supporting FOSS, I feel much more confident in that support being sustained long-term when it aligns with some profit motive.
IMO the best case is that Qualcomm sees dollar signs when they imagine their Oryon CPUs and Adreno GPUs dominating the consumer linux landscape. There is definitely room to shake up x86 (especially when it comes to perf/W and idle battery drain), and only a finite window for ARM to do so with RISC-V on the horizon.
And to whatever extent Qualcomm et al now view Linux as a relevant personal computing platform, I think a massive amount of credit goes to Valve. I seriously doubt Linux support even enters the conversation at these companies without the Steam Deck's success.
> When you get new hardware and new features, you don’t want them sitting idle while you wait for patches to get upstreamed. Whether you develop for IoT, automotive, audio or mobile, when you get new features in a system-on-chip (SoC), you want to take advantage of them right now.
Sure doesn’t sound like mainstream consumer pc desktop is the target at all. Yes, they do provide instructions for how to run this on desktop but it’s far from accessible for the overwhelming majority of pc users.
I mean it’s still a good thing for Linux desktop to have this as an option, I’m not complaining. But to be realistic those benefits feel tangential to what Qualcomm is aiming at here.
Fully agree. When I said "consumer linux landscape" & "personal computing platform" I was thinking much more broadly than desktop PCs.
Admittedly a hypothetical Arm-based Steam Deck or Framework Laptop were at the forefront of my mind, but I think any consumer product running linux qualifies, be it "IoT, automotive, audio or mobile".
Whether people are buying EVs with a slick linux-based infotainment screens, gaming handhelds running SteamOS, or smart-devices with fancy local AI features, I think the effect is the same. If Qualcomm predicts significant growth in demand for efficient, high perf devices running customized Linux distros, I think it could be great for FOSS at large.
Woah, this is amazing. I’ve been looking for an ARM Linux machine for a while and ended up about to get M2 Pros in a rack running Asahi. It has been near impossible to get a Snapdragon Elite machine. The IdeaCentre or whatever is 2x the cost / performance and as far as I know is poorly supported.
This changes the game. I’d rather use native Linux than Asahi (though the latter is amazing).
This might sound silly question, but those of you who have digits/spark machine, has anyone run Fedora on it? I kind of ran away from Ubuntu back to Fedora because reasons. Bonus question, far-fetched, steam and games with FEX?
The drivers, while impressively reverse-engineered, are basically alpha-quality by Linux standards. Even well-studied M1 machines will have spotty support in comparison to what an OEM can provide officially.
I don't think this changes the game as much as you think.
AFAIU, the biggest challenge of running Linux on ARM machines is supporting the devicetree of each machine. After all, there is mainline kernel support for previous Qualcomm chips, yet very few machines with those chips can actually run Linux distros.
So this is good news, but in practical terms it's just a marketing piece.
Has Qualcomm seen the light after working with Valve on Steam Frame? The news that Steam Frame would be running an open source Adreno GPU driver really caught me by surprise.
My impression from the emulation folks is that the proprietary drivers are chock full of problems. I suspect it was open source drivers or nothing (i.e., back to an AMD x86 solution like the Steam Deck).
(And I don't think Qualcomm has seen the light - my understanding is that the Turnip drivers are purely reverse engineered.)
They are, but that's hardly unique to Qualcomm. Tons of hardware with "proper" upstream Linux drivers still requires closed-source firmware blobs, and in particular with anything wireless that's probably an unwinnable battle due to regulatory constraints.
Does that mean that one will be able to purchase tablets with this chip and replace the OS with Linux?
That would be great. As far as I know, there currently are no options for lightweight tablets that support Linux.
Not sure how well WSL2 on tablets work. Does anybody here have experiences with WSL2 on tablets like the new Microsoft Surface Pro that uses the Snapdragon X Elite chip?
I think the performance of x86 VMs would be pretty poor anyway due to the high overhead of TSO emulation. Windows ARM doesn't have the benefit of hardware assistance like macOS does, and the tricks that Microsoft came up with to mitigate the impact rely on metadata that only MSVC emits, so anything compiled with GCC or LLVM would always hit their emulators slow path.
I really hope this is the case because I’d love to have an arm64 laptop for work. Then binaries in my laptop will work on my embedded systems, generally.
560g is fine. But I wouldn't want to work on a 11.5" device. Something between 13" and 14" is my preferred size.
And I would want to do a normal Debian stable installation. Just like I can on a Lenovo laptop. The Librem 11 comes with their own Debian based distro and I can't find any info if I can install a normal Debian on it from scratch.
Sorry. I don't trust these guys. Some of my Linux laptops use their wireless hardware and the drivers are so poor that, YEARS later, Wi-Fi still doesn't work right.
i'm using Linux just fine on an ARM desktop for a long time, via Apple Silicon hypervisor enabled via the UTM macos app (which wraps both Qemu, which i don't use, and Apple Silicon hypervisor, which i do use, configurable when instantiating a new image from an iso).
i mention this because perhaps you'd like it too. in my case fedora 43 works just fine, and fast.
tbh I don't mind it so much on corporate blogs, it mainly grinds my gears when people choose to do it in (what would otherwise be) more personal writing.
Does KVM hypervisor work? Previous Qualcomm CPUs have locked hypervisor mode behind Qualcomm proprietary blobs, and only allowed HyperV to use it - this was definitely the case for WOS laptops.
I worked at Linaro, who was contracting for Qualcomm. Qualcomm were pushing for some protected hypervisor called Gunyah (which had its own Linux interface and needed a new qemu port) that apparently no one liked. I tried to port it to KVM [1], but upstream folks (mostly Google) outright rejected the port. Otherwise KVM would have been available on QCOM boards. You can still try it. I have a Linux kernel and a Qemu port on my github [2,3]
Upstream would accept a patchset that exposed an independent Gunyah-specific UAPI (why not the same one as downstream — crosvm already supports that) instead of pretending to be KVM (it's not a "port", you can't port a hypervisor to a hypervisor).
KVM is available on current compute platforms (laptops) if you escape to EL2 via slbounce; and on Glymur (X2E) it will be available by default (yay!).
MS Windows had an exclusive period for X1, but Google will support Android and ChromeOS on Qualcomm X2-based devices in 2026, which would require the pKVM/KVM hypervisor used by Android, https://news.ycombinator.com/item?id=45368167
While we are at Snapdragon processors ... Does anyone know what (not so technical-)user friendly distro runs without too many issues on a Snapdragon 850? I found Mobian listing Snapdragon 845, but I don't know at all, if that is almost the same or not compatible at all.
I explored their site, but they only list supported devices, not supported CPUs, which leaves me guessing, whether their OS even works on this CPU. And since I don't really know that, it seems to be a lot of effort needed to use their tooling for non-supported devices, to make an installation image. Though I have not tried that yet. It only made me doubt, whether I could succeed that way.
Can you buy this chip or is it only for Android phones? They have bad support for what you can buy (X Elite) but now they're touting upstreaming the chip you can't buy?
Oryon v3 is designed for actual PC usage, not phones. But they aren't shipping until H1 next year. This is just a heads-up memo about Linux support, in that regard. Which is nice, I guess?
Just in case anyone's tempted to buy one of these now: Support is alright after heroic (and continuing) efforts to improve platform support, but it's flaky. M1/M2 devices offer better performance and the state of Asahi drivers is much better, particularly around audio.
I don't know much about ARM SoCs, is this something you would built a phone with? With all the talk about Google locking down Android, can Pine64 please go and make a Pinephone with this if that brings us closer to a Linux phone?
Snapdragon X Elite laptops have been out for the last two years, if not more. How much has Qualcomm did over this time to make Linux work on those devices - almost nothing. As of 2 months ago, the best you could do was a special cut of Ubuntu that kinda sorta booted on those machines and required Windows to be present in order to pull some drivers.
So how about you give me a fucking break, Qualcomm? Call back when Snapdragon has first class support in major distros and you are serious about Linux.
Qualcomm actually contributes code whereas Apple's contributions begin and end at "you can boot software not signed by Apple". It's hardly a comparison.
The problems seem rather similar, a while after release you need a dedicated build to actually get Linux working mostly right. Doesn't come close to the normal Linux experience. Then again, the X1 Extreme seems to have USB display and thunderbolt support, so they're better than Apple Silicon will probably ever be on Linux.
Eh. The CPU might be supported in Linux, but all of the rest of the hardware to make a laptop is left dangling in the wind. Look at the X1E laptops to see how far "upstream Linux support for a CPU" gets you.
They aren't targeting enthusiasts with this announcement.
X1E laptops have fully working DisplayPort+USB3+USB2+PD over USB-C unlike Asahi Macbooks :p There really aren't that many gaps in X1E laptop support left.
EL2 is coming by default on Glymur (X2E) (yaaaay), can be enabled in config on some IoT platforms, and can be booted into via Secure Launch on previous compute platforms (Hamoa/Purwa aka X1E/X1P, SC8280XP), search for slbounce.
On phone platforms.. probably not? Or Android might want it for pKVM..
> The Adreno user mode driver (UMD) from Qualcomm Technologies is available as a downloadable Debian package and provides Vulkan 1.4 API support as well as the necessary GPU-related firmware.
Are they already using Turnip / Mesa as their Vulkan implementation or not yet? If not, they should. Valve are using Turnip on their Steam Frame.
That would be another step of working with upstream, besides the kernel driver.
Please don't perpetuate political battle or make personal attacks on people on HN, no matter how right you are or feel you are. The topic of this thread is "Same-day upstream Linux support for Snapdragon 8 Elite Gen 5 mobile platform". Let's keep comments on that topic, and definitely not pollute it with personal attacks on individuals over the actions of their government. In case there's any perception that I'm "taking sides", I've replied to the commenter who initiated this subthread too, but it's not OK to reply to a bad comment with another bad one.
If anybody in Qualcomm leadership is reading this thread: this is a good start, and I applaud you for it. There is also a lot more to do if you're serious about growing your market penetration beyond phones.
The drivers might be up on LKML, but they're not mainlined yet. And this is just gen5. It would be great if you could fix your gen4 and 4.5 drivers, so that people building products with your chips weren't stuck on an orphaned vendor kernel that doesn't even upstream to your public fork.
Also your boot-chain is still closed and proprietary, and completely different than the one used by all other ARM vendors. Being the special snowflake is not helping your business or your customers.
And don't even get me started on Gunyah and GearVM, or on the proprietary, locked nature of your BSP, or how far behind TI and NXP you are on software quality and ease of use. Maybe also consider releasing some actual documentation on your chips.
I know multiple developers who have sworn off Qualcomm and will never design with your chips again at any price point. Your closed-off support model is 100% the culprit, and it hurts your core business. Any software support revenue that you managage to extract comes at the cost of goodwill and future chip sales.
Your chips are good - best in the industry. If you can up your software game to match, you'll really meet your potential.
> Also your boot-chain is still closed and proprietary
Nowadays the entire thing until you land in EL1 needs to be signed by Qualcomm as well. This is without "Secure Boot" enabled. OEMs only get to run code under the hypervisor. And you might want to use a part of the hardware but someone decided the VM your code runs in shouldn't have access to that, too bad.
not all true. And Qualcomm taking over EL2 is optional now
4 replies →
> ... Also your boot-chain is still closed and proprietary, and completely different than the one used by all other ARM vendors. Being the special snowflake is not helping your business or your customers. ...
Why does the boot-chain matter? Can't we just have a custom U-Boot implementation that interacts with the bespoke boot chain while providing standard UEFI support to the rest of the system? Isn't that how Asahi works?
It matters when you're doing custom hardware, or when you're designing a product where boot speed matters, or when you need to implement something special.
A full-featured U-Boot implementation would be fine IMO. But for the generations that I've used, that's not on the table. What we get is a proprietary flow through a proprietary hypervisor into a fork of Android's bootloader (even if vanilla Linux is the target OS). There's no way to control startup boot options, and no way to use KVM, Xen or any hypervisor except the proprietary one that's also part of the boot chain.
This doesn't lend itself to flexible products, or to products that are easy for a company to design or support. That is why things like this happen: https://news.ycombinator.com/item?id=46008156
1 reply →
Aside from the sibling comments, it also matters that you need to be able to review it if you need to build a truly "secure" product. History is littered with broken, unfixable secure boot implementations.
Because a computer isn't just a processor. It has to interact with an EC, IO controllers, and whatnot, and if you don't have control over the boot chain, all of that stuff becomes an even bigger PITA than it already is.
> And don't even get me started on Gunyah and
Gunyah is disappearing from new chips, slowly but surely.
X2 doesn't have it anymore, the IoT range has it as optional now. And it's going to be deployed less from there
Awesome, that's great to hear. Now if Qualcomm would only relax the walls between their business units, their other customers could benefit as well.
Who benefits from having separate BUs maintain fully separate software stacks? It's duplicated, wasted effort on Qualcomm's part. Maybe it lets them double-charge their customers for this duplicate effort, but that feels short-sighted. It leaves a bad taste in their customers' mouths. And there's certainly no benefit in delivered software quality.
Qualcomm should be making it easy for everybody to buy and use their chips, not artificially segmenting every single customer. They could sweep the market so hard if they were just a little less greedy.
Thanks for the constructive framing. My gut reaction was "great job, you're doing the minimum"
If I was to guess, id say someone did this as a side project at QC because maybe they like FOSS and want to give something back. Given the partnership between QC and MSFT for laptops and Google for android, I won't be surprised if we never see interest from QC for any real linux hardware.
1 reply →
Second best, after Apple.
Apple, whose FOSS support is reliant on volunteers reverse engineering their shit?
This is much better than that. Not great yet, but much better than that in comparison.
2 replies →
https://en.wikipedia.org/wiki/Qualcomm#2015–2024:_NXP,_Broad...
Yeah that page smells like a pr stunt.
Go all in or go home, qualcomm.
You'd rather have nothing it seems.
1 reply →
Qualcomm did this in 2024. They pushed some patches to LKML, and issued a press release to brag about it. (https://www.qualcomm.com/developer/blog/2024/05/upstreaming-...)
Yet 2 days ago, Tuxedo Computers announced they were abandoning Qualcomm due to crap support. (https://www.theregister.com/2025/11/26/tuxedo_axes_arm_lapto...).
There is nothing in this press release to suggest they've changed.
Isn't Tuxedo jus a white label reseller?
White label reseller isn't really the right term. They don't design most of their components and buy them wholesale, but they do assemble them and most relevant to this particular comment thread, they do a lot of the device firmware and support stuff.
It's exactly the stuff that they actually do themselves that Qualcomm has been making very hard.
>Yet 2 days ago, Tuxedo Computers announced they were abandoning Qualcomm due to crap support. (
Does Apple offer better support? Qualcomm offers commercial support. I guess Tuuxedo Computers didn't pay for the support?
Apple is a non-sequitur. Tuuxedo is giving up on Qualcomm in favor of AMD and Intel.
Do AMD and Intel require Tuuxedo to pay for premium support in order to get working Linux drivers? No, of course not.
Qualcomm's support for Linux is embarrassing when you compare it to pretty much any processor manufacturer except Apple.
2 replies →
Macs have an open bootloader that allows users to run an unsigned OS like Asahi Linux (without having it degrade security when you do boot MacOS).
As someone who uses Mobile Linux, I am pretty excited to see this, but I can't help but wonder if this is only a "Business decision" and not necessarily Qualcomm turning over a new leaf for being FOSS friendly:
- Their Snapdragon X laptop didn't do very well, and they likely realize an ARM Windows laptop will always be a second class citizen: https://www.techpowerup.com/329255/snapdragon-x-failed-qualc... .
- Likewise, Mobile SoCs are completely dependent on Android without proper upstreaming (which they haven't done in the past).
- They are seeing Valve spending time and money on FOSS support paying off, especially with their new hardware releases.
On the other hand, proper upstreaming of the chips give them much more flexibility for different linux-based OSes.
I'm personally rooting for "business decision" over "turning over a new leaf".
If FOSS support is motivated by a clear profit motive, then it'll be viewed positively by shareholders and stick around no matter who is in charge. If FOSS support comes from "turning over a new leaf", it could be dropped at a moment's notice in response to a leadership change.
IMO we will always see far better FOSS support from the private sector when the time they invest has a positive ROI that is obvious and easy to brag about in a quarterly earnings call.
Incentives trump feelings for publicly traded companies 99 times out of 100. People constantly anthropomorphize them, but they aren't people (regardless of similarities in the law), and they definitely don't act like people, at least normal ones. At best, you can view them as something like a sociopath. I wouldn't look at a sociopath acting nicer and think "oh, they turned over a new leaf" because they aren't just going to change how their mind works, I'd think "oh, they found a reason to act in a way I like for the time being. I hope it isn't short lived."
8 replies →
Snapdragon does poorly I think because it's a bet if it works or not. Windows runs things seamlessly other than OpenGL (it can run that too but it's not anything strait forward - needs the gl to dx store app thing) but the other reason is cost. for the premium business laptop most buyers (business) won't budge off Intel even because of the "no one got fired for buying IBM" mentality at the big Enterprises Ive been at.
I will say with my 8 gen 3 snapdragon I'm impressed and also disappointed - stupid thing needs active cooling and I'm pretty sure it's bad enough that it's desoldered or damaged the core or something from heat but also you can't get driver updates for the GPU if you wanted because Qualcomm be the way it do.
Driver update depends on your OEM. Both ARM and Qualcomm send driver updates for their premium and upper highend Socs. The support reaching your phone is on the OEM. Google has started to push direct GPU driver updates starting with Pixel 10. So, hopefully others may follow too.
4 replies →
I've used basically every Windows on Arm machine - I actually quite like my X Elite ThinkPad T14s Gen6, compared the the X13s - feels like they got everything right, that the X13s got wrong
3 replies →
Of course it's a "business decision". Companies don't do things for any other reason. They see a benefit to upstreaming in this instance, and will do it again (or not) depending on whether or not they expect to see benefits in the future.
This is no different from any other company that has "embraced" open source.
I'd imagine it's purely because not doing it turned out to be PITA in the long term.
As with pretty much all other ARM cpu vendors that pushed for their own kernel fork just to have drivers that did not need to be okayed by mainstream kernel, it was faster iteration to deliver something working to their clients; but it was also PITA to their clients, especially when industry started demanding longer support for their devices
It'll probably be as much of a second class citizen elsewhere (the real problem is the hardware hasn't as good as Apple Silicon laptops but has been in the same price class at the bottom) but it's good they chase everywhere rather than just one use case.
In the case of Linux, that issue is solely because of non-upstreamed drivers. With that, it can be a first class citizen just like any other processor.
3 replies →
Their problem was that they had the performance claims and marketing of Apple but the implementation of Microsoft Teams. Apple M1 was shaky but all the groundwork was there and it took off. Qualcomm was highly questionable at best.
> Microsoft leads the adoption of the Snapdragon X, having integrated the platform across much of its Surface lineup
https://www.microsoft.com/en-us/surface/devices/surface-lapt...
it makes some sense for embedded stuff, linux is only continuing to gain ground there.
are there any linux phone projects that are actively maintained and used in 2025? i was under the impression that android kinda subsumed them all.
Software-wise: Ubuntu Touch, PostmarketOS, and Mobian are all actively maintained. Ubuntu Touch uses Lomiri as its UI which is somewhat bespoke (though they're working on disentangling it from the distro for packaging elsewhere), the others use various mobile Linux UIs (and there's a surprisingly large variety of options there).
Librem5 and Jolla are actively developed
A businesss decision would be great. What would suck would be a marketing decision.
Today’s marketing decisions are tomorrow’s business decisions.
1 reply →
> Their Snapdragon X laptop didn't do very well, and they likely realize an ARM Windows laptop will always be a second class citizen
Why? So far ARM laptops provide either vastly better battery life for the same performance or vastly better performance for the same battery life. Even versus discrete GPUs.
Within a couple years from now you're gonna look like an utter fool for buying x86 (and Nvidia / AMD / Intel GPU) unless Intel, AMD and Nvidia really pull their head out of the sand.
There's a few specific workloads like local LLM and legacy where you'd want a discrete GPU or x86, but otherwise it is looking like GG.
Are you sure? I've recently watched a video where presenter mentioned how Lunar Lake based laptops are better then any Snapdragon.
For example https://www.pcworld.com/article/2463714/tested-intels-lunar-...
1 reply →
Can't say about windows, but Linux is spotty despite the loud announcement about official upstream Linux support
https://www.tuxedocomputers.com/en/Discontinuation-of-ARM-no...
I hope this is motivated by shrewd decision-making in response to market pressure, as opposed to being strictly a perception thing.
While it would be great for Qualcomm to "do the right thing" in supporting FOSS, I feel much more confident in that support being sustained long-term when it aligns with some profit motive.
IMO the best case is that Qualcomm sees dollar signs when they imagine their Oryon CPUs and Adreno GPUs dominating the consumer linux landscape. There is definitely room to shake up x86 (especially when it comes to perf/W and idle battery drain), and only a finite window for ARM to do so with RISC-V on the horizon.
And to whatever extent Qualcomm et al now view Linux as a relevant personal computing platform, I think a massive amount of credit goes to Valve. I seriously doubt Linux support even enters the conversation at these companies without the Steam Deck's success.
> When you get new hardware and new features, you don’t want them sitting idle while you wait for patches to get upstreamed. Whether you develop for IoT, automotive, audio or mobile, when you get new features in a system-on-chip (SoC), you want to take advantage of them right now.
Sure doesn’t sound like mainstream consumer pc desktop is the target at all. Yes, they do provide instructions for how to run this on desktop but it’s far from accessible for the overwhelming majority of pc users.
I mean it’s still a good thing for Linux desktop to have this as an option, I’m not complaining. But to be realistic those benefits feel tangential to what Qualcomm is aiming at here.
Fully agree. When I said "consumer linux landscape" & "personal computing platform" I was thinking much more broadly than desktop PCs.
Admittedly a hypothetical Arm-based Steam Deck or Framework Laptop were at the forefront of my mind, but I think any consumer product running linux qualifies, be it "IoT, automotive, audio or mobile".
Whether people are buying EVs with a slick linux-based infotainment screens, gaming handhelds running SteamOS, or smart-devices with fancy local AI features, I think the effect is the same. If Qualcomm predicts significant growth in demand for efficient, high perf devices running customized Linux distros, I think it could be great for FOSS at large.
1 reply →
Woah, this is amazing. I’ve been looking for an ARM Linux machine for a while and ended up about to get M2 Pros in a rack running Asahi. It has been near impossible to get a Snapdragon Elite machine. The IdeaCentre or whatever is 2x the cost / performance and as far as I know is poorly supported.
This changes the game. I’d rather use native Linux than Asahi (though the latter is amazing).
Get a DGX spark.
Ships with aarch64 Ubuntu 24.04.
Tons of cores and RAM.
Very quiet and small
UEFI bootloader - I installed Ubuntu 25.10 and ESXi arm edition just by booting the ISO
usb-c power input (kinda cool)
Insane connectx 200GbE RoCE networking
10GbE Ethernet
Oh and an nvidia gpu with cuda and access to 128GB of unified memory
It would be perfect if it had some kind of BMC or IPMI/redfish and an exposed PCIE slot. But this thing is an awesome arm64 workstation no doubt.
May try to install to a USB drive and hang another gpu off the nvme port just to see what happens
And, any other options or recommendations if I don't need the huge GPU?
Seems like the middle ground between SBCs and huge servers is a bit underserved in ARM...
This might sound silly question, but those of you who have digits/spark machine, has anyone run Fedora on it? I kind of ran away from Ubuntu back to Fedora because reasons. Bonus question, far-fetched, steam and games with FEX?
2 replies →
Oh that's a good shout. A friend did get one of these so I'll go take a look at it and see what it's like.
It seems incredible but uhm, way out of my mitteleuropaishe budget
Is it easy to buy a DGX Spark?
1 reply →
Does this actually translate into any kind of probability of a manufacturer making a device with this chip?
How is Asahi not native?
Presumably OP meant a Linux distro using a normal upstream kernel?
The drivers, while impressively reverse-engineered, are basically alpha-quality by Linux standards. Even well-studied M1 machines will have spotty support in comparison to what an OEM can provide officially.
6 replies →
I don't think this changes the game as much as you think.
AFAIU, the biggest challenge of running Linux on ARM machines is supporting the devicetree of each machine. After all, there is mainline kernel support for previous Qualcomm chips, yet very few machines with those chips can actually run Linux distros.
So this is good news, but in practical terms it's just a marketing piece.
Has Qualcomm seen the light after working with Valve on Steam Frame? The news that Steam Frame would be running an open source Adreno GPU driver really caught me by surprise.
My impression from the emulation folks is that the proprietary drivers are chock full of problems. I suspect it was open source drivers or nothing (i.e., back to an AMD x86 solution like the Steam Deck).
(And I don't think Qualcomm has seen the light - my understanding is that the Turnip drivers are purely reverse engineered.)
Qualcomm has several full time employees working on Mesa (Freedreno/Turnip). They probably must have access to some documentation now..
They've been working on better mainline Linux support for a while now, but their last generation is still catching up on the driver side of things.
I hope they succeed but the last generation has only recently become mostly usable for specific distros. General support may take a while.
I just checked: Frame is Gen 3 and the article is Gen 5.
I am really hoping Valve will release a Frame Pro with Elite Gen 5 later :(
2 replies →
The frame uses X Elite, their SoC designed or Laptops. These drivers are for mobile Line. Yeah the naming can be quite confusing.
2 replies →
It wouldn't surprise me if they're full of binary blobs
They are, but that's hardly unique to Qualcomm. Tons of hardware with "proper" upstream Linux drivers still requires closed-source firmware blobs, and in particular with anything wireless that's probably an unwinnable battle due to regulatory constraints.
4 replies →
Does that mean that one will be able to purchase tablets with this chip and replace the OS with Linux?
That would be great. As far as I know, there currently are no options for lightweight tablets that support Linux.
Not sure how well WSL2 on tablets work. Does anybody here have experiences with WSL2 on tablets like the new Microsoft Surface Pro that uses the Snapdragon X Elite chip?
https://www.windowscentral.com/software-apps/how-well-does-w...
Apparently WSL2 does work, it pulls a native ARM64 Linux distro and then proceeds as usual.
I have the 8 gen 3 and wsl and hyperv work fine just can't really use x86 binaries / containers / operating systems.
I think the performance of x86 VMs would be pretty poor anyway due to the high overhead of TSO emulation. Windows ARM doesn't have the benefit of hardware assistance like macOS does, and the tricks that Microsoft came up with to mitigate the impact rely on metadata that only MSVC emits, so anything compiled with GCC or LLVM would always hit their emulators slow path.
2 replies →
I really hope this is the case because I’d love to have an arm64 laptop for work. Then binaries in my laptop will work on my embedded systems, generally.
The Linux support on the X1E today is lacking. I’m much more optimistic for the X2E.
The hardware is great, though, I love the 12” Surface with the X1E. WSL2 works great!
> As far as I know, there currently are no options for lightweight tablets that support Linux.
Does this count? https://puri.sm/products/librem-11
560g is fine. But I wouldn't want to work on a 11.5" device. Something between 13" and 14" is my preferred size.
And I would want to do a normal Debian stable installation. Just like I can on a Lenovo laptop. The Librem 11 comes with their own Debian based distro and I can't find any info if I can install a normal Debian on it from scratch.
1 reply →
> Hardware-accelerated video playback of H.264 (AVC), H.265 (HEVC) and VP9 video streams
> Hardware-accelerated video recording into H.264 (AVC) and H.265 (HEVC) formats
no mention of AV1? Surprised since most websites including YT uses it heavily.
The Qualcomm marketing spec sheet mentions AV1 decoding: https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets...
Maybe that part of the driver isn't finished yet?
Yes. It is on the mailing list: https://lore.kernel.org/all/20251001-av1_irisdecoder-v1-0-9f...
It actually introduces new things into the UAPI because no one else did fully-stateful AV1 decode before.
Or licensed.
6 replies →
Sorry. I don't trust these guys. Some of my Linux laptops use their wireless hardware and the drivers are so poor that, YEARS later, Wi-Fi still doesn't work right.
I wish this signup box did not cover the text, or at least there was some way to close/remove it.
I use uBlock Origin blocked the container element, problem solved.
yeah i had to inspect element and delete the html node. theres a double-space in the first line of the top summary section.
presentation is half the message!
the year of linux on the arm desktop cannot come soon enough
also, not to beat a horse that is by now six feet under, but
> No delays, no hurry-up-and-wait, no registration. Just go get the new features.
i'm so tired
i'm using Linux just fine on an ARM desktop for a long time, via Apple Silicon hypervisor enabled via the UTM macos app (which wraps both Qemu, which i don't use, and Apple Silicon hypervisor, which i do use, configurable when instantiating a new image from an iso).
i mention this because perhaps you'd like it too. in my case fedora 43 works just fine, and fast.
Ooh, thank you for this, I might try it on my m4 mac. Any tips or anything I should be aware of?
1 reply →
what's the battery life like?
do you use macos at all, or do you do ~everything within a full-screened fedora instance?
1 reply →
How does Fedora handle the graphics and audio when running under hypervisor? Or is it strictly a command-line thing?
1 reply →
the year of linux desktop is called steamdeck
tbh I don't mind it so much on corporate blogs, it mainly grinds my gears when people choose to do it in (what would otherwise be) more personal writing.
Does KVM hypervisor work? Previous Qualcomm CPUs have locked hypervisor mode behind Qualcomm proprietary blobs, and only allowed HyperV to use it - this was definitely the case for WOS laptops.
I worked at Linaro, who was contracting for Qualcomm. Qualcomm were pushing for some protected hypervisor called Gunyah (which had its own Linux interface and needed a new qemu port) that apparently no one liked. I tried to port it to KVM [1], but upstream folks (mostly Google) outright rejected the port. Otherwise KVM would have been available on QCOM boards. You can still try it. I have a Linux kernel and a Qemu port on my github [2,3]
[1] https://lore.kernel.org/kvm/20250424141341.841734-1-karim.ma...
[2] https://github.com/karim-manaouil/linux-next/tree/gunyah-kvm
[3] https://github.com/karim-manaouil/qemu-for-gunyah
Upstream would accept a patchset that exposed an independent Gunyah-specific UAPI (why not the same one as downstream — crosvm already supports that) instead of pretending to be KVM (it's not a "port", you can't port a hypervisor to a hypervisor).
KVM is available on current compute platforms (laptops) if you escape to EL2 via slbounce; and on Glymur (X2E) it will be available by default (yay!).
1 reply →
MS Windows had an exclusive period for X1, but Google will support Android and ChromeOS on Qualcomm X2-based devices in 2026, which would require the pKVM/KVM hypervisor used by Android, https://news.ycombinator.com/item?id=45368167
The original Oryon systems allowed you to boot directly into EL2 and skip Gunyah via BIOS settings. I assume this will be the same.
Which ones, where? On X1 laptops that shipped with Windows, you can only escape into EL2 via Secure Launch: https://github.com/TravMurav/slbounce
1 reply →
I appreciate the gesture, but... just release the docs!
Of course, there would exist something like Qualcomm Linux,
https://www.qualcomm.com/developer/software/qualcomm-linux
While we are at Snapdragon processors ... Does anyone know what (not so technical-)user friendly distro runs without too many issues on a Snapdragon 850? I found Mobian listing Snapdragon 845, but I don't know at all, if that is almost the same or not compatible at all.
Tried postmarketOS yet?
I explored their site, but they only list supported devices, not supported CPUs, which leaves me guessing, whether their OS even works on this CPU. And since I don't really know that, it seems to be a lot of effort needed to use their tooling for non-supported devices, to make an installation image. Though I have not tried that yet. It only made me doubt, whether I could succeed that way.
1 reply →
Can you buy this chip or is it only for Android phones? They have bad support for what you can buy (X Elite) but now they're touting upstreaming the chip you can't buy?
Oryon v3 is designed for actual PC usage, not phones. But they aren't shipping until H1 next year. This is just a heads-up memo about Linux support, in that regard. Which is nice, I guess?
I'm still mad about their lack of support for the 8cx gen 3. It's one of the first laptop SKUs they put out and support still isn't great.
The Lenovo x13s works pretty nicely these days, EL2 support aside. What problems have you faced?
Just in case anyone's tempted to buy one of these now: Support is alright after heroic (and continuing) efforts to improve platform support, but it's flaky. M1/M2 devices offer better performance and the state of Asahi drivers is much better, particularly around audio.
See qebspil for filling the gap for the EL2 side
As far as I know, at least the modem support is half-baked or still non-functional.
What's the use case here? Mobile that can use Linux instead of Android? Is that possible?
Since OpenMoko, the thing is that the market doesn't care.
https://en.wikipedia.org/wiki/Openmoko
I don't know much about ARM SoCs, is this something you would built a phone with? With all the talk about Google locking down Android, can Pine64 please go and make a Pinephone with this if that brings us closer to a Linux phone?
How far away are we from being able to use new snapdragon laptops with Linux?
I'm pretty keen to play around with Proton, FEX in a laptop that rivals the MBP
Snapdragon X Elite laptops have been out for the last two years, if not more. How much has Qualcomm did over this time to make Linux work on those devices - almost nothing. As of 2 months ago, the best you could do was a special cut of Ubuntu that kinda sorta booted on those machines and required Windows to be present in order to pull some drivers.
So how about you give me a fucking break, Qualcomm? Call back when Snapdragon has first class support in major distros and you are serious about Linux.
I’d like to see the chips powering the new Surface devices in a Framework laptop at some point. Feel like they would be perfect for the Framework 12
How does it compare to Apple ARM M series and did they slap on a decent GPU? If not, they still got a long way to go...
Qualcomm actually contributes code whereas Apple's contributions begin and end at "you can boot software not signed by Apple". It's hardly a comparison.
The problems seem rather similar, a while after release you need a dedicated build to actually get Linux working mostly right. Doesn't come close to the normal Linux experience. Then again, the X1 Extreme seems to have USB display and thunderbolt support, so they're better than Apple Silicon will probably ever be on Linux.
Eh. The CPU might be supported in Linux, but all of the rest of the hardware to make a laptop is left dangling in the wind. Look at the X1E laptops to see how far "upstream Linux support for a CPU" gets you.
They aren't targeting enthusiasts with this announcement.
X1E laptops have fully working DisplayPort+USB3+USB2+PD over USB-C unlike Asahi Macbooks :p There really aren't that many gaps in X1E laptop support left.
Docs though?
Actual bare metal Linux or under a hypervisor? I thought Qualcomm used a hypervisor to isolate the Linux environment that is taken for granted on x86.
EL2 is coming by default on Glymur (X2E) (yaaaay), can be enabled in config on some IoT platforms, and can be booted into via Secure Launch on previous compute platforms (Hamoa/Purwa aka X1E/X1P, SC8280XP), search for slbounce.
On phone platforms.. probably not? Or Android might want it for pKVM..
_Current_ phone platforms still use Gunyah.
> The Adreno user mode driver (UMD) from Qualcomm Technologies is available as a downloadable Debian package and provides Vulkan 1.4 API support as well as the necessary GPU-related firmware.
Are they already using Turnip / Mesa as their Vulkan implementation or not yet? If not, they should. Valve are using Turnip on their Steam Frame.
That would be another step of working with upstream, besides the kernel driver.
Mesa MR for a8xx is coming. It's just not done yet. But they have full time employees working on Mesa.
Oh, that's good!
ex-qcom engineer here, asking qcom for open source support is like asking financial advices in a casino.
let's stop being naive - qcom will not change.
[flagged]
[flagged]
This makes no sense. Just imagine you would get handcuffed tomorrow. Collateral damage. Blame some guy. Or a gal.
10 replies →
Because other people do bad things these people aren't allowed to share ideas.
[flagged]
6 replies →
[flagged]
[flagged]
2 replies →
[flagged]
1 reply →
I tried to get it on archive.is but it say in a loop forever.
Even when it's not blocked, the layout is broken...
[flagged]
Please don't perpetuate political battle or make personal attacks on people on HN, no matter how right you are or feel you are. The topic of this thread is "Same-day upstream Linux support for Snapdragon 8 Elite Gen 5 mobile platform". Let's keep comments on that topic, and definitely not pollute it with personal attacks on individuals over the actions of their government. In case there's any perception that I'm "taking sides", I've replied to the commenter who initiated this subthread too, but it's not OK to reply to a bad comment with another bad one.
[dead]