Qualcomm Linux 2.0
72 points
7 hours ago
| 3 comments
| qualcomm.com
| HN
LorenDB
6 hours ago
[-]
And here I was hoping they'd decided to support Linux on the Snapdragon X2 chips.
reply
wmf
5 hours ago
[-]
reply
diabllicseagull
1 hour ago
[-]
From the June 4th article: "These patches are a result of a collaboration between a couple of Qualcomm engineers taking part in an internal sprint and were created over 3 days."

it's not giving me any warm and fuzzy.

reply
aseipp
1 hour ago
[-]
They've been upstreaming drivers for the X2 platform for months at this point, since at least late 2025 (just search "glymur" or "kaanapali" on LKML).

The patch referenced in the Phoronix article is just a device tree file. That is the easiest part of the whole thing. As usual he's just farming every random LKML patch he can for clicks.

reply
wmf
42 minutes ago
[-]
The open source world has a habit of leaving the easiest part of the whole thing unfinished for years or decades, so I salute this patch and I salute Phoronix for calling attention to it.
reply
aseipp
23 minutes ago
[-]
Point well taken.
reply
senectus1
4 hours ago
[-]
holy hell.. the price tags...!
reply
geerlingguy
4 hours ago
[-]
$4,300-$6,000+, wow you're not wrong. And that's just 32 or 64 GB of RAM.
reply
wmf
4 hours ago
[-]
Something has gone wrong at HP. They are also charging $7,000 for Strix Halo.
reply
esseph
1 hour ago
[-]
HP is nuts

HPE I've had very good luck with for HCI.

reply
_fzslm
5 hours ago
[-]
I have a gorgeous Surface Pro 11 X1 Elite that can run just enough Linux to tease me with how beautiful it could be, but it's still unstable enough that I can't daily it.

Torture.

reply
pylotlight
3 hours ago
[-]
It's really that weak?
reply
keyle
4 hours ago
[-]
I recently tried to get BSD/Linux to work on my omnibook X 14 and... it's been a journey!

Eventually I got it to work well with [1] and extracted firmware off github because I had wiped Windows and all partitions into oblivion.

I was looking for the bliss of fan-less linux with ARM. The joy! [2]

[1] https://discourse.ubuntu.com/t/ubuntu-concept-snapdragon-x-e...

[2] the fans are ON permanently

reply
mrheosuper
4 hours ago
[-]
If you want fanless arm linux machine, why not macbook m2 air + asahi linux ?
reply
jjtheblunt
2 hours ago
[-]
apple silicon is virtualization capable and the UTM app (on the app store, but open source so you can build it too) wraps Apple's hypervisor framework, allows me to run on my macbook air (m2 earlier, recently updated to m5 just to get more memory) macos as well as arm versions of both fedora and arch, with plasma and gnome (and i've used hyprland etc to toy around).

it's important to set UTM to use Apple Silicon _virtualization_, because otherwise it uses QEMU and is thereby emulating. With Apple Silicon virtualization, having macos and arch and fedora all going at once is amazing.

pertinent references :

https://github.com/utmapp/UTM

or search for UTM on the Apple app store, where it's prebuilt (and that's what i use successfully).

https://developer.apple.com/documentation/hypervisor

reply
pseudosavant
3 hours ago
[-]
Asahi still doesn't support a lot of basic things like: external displays, Thunderbolt, hardware accelerated video decoding, 120hz refresh rate, etc.
reply
keyle
4 hours ago
[-]
Because at the time of my purchase I mistakenly believed that fan-less was a given for an ARM laptop; and that ARM laptops were a lot more supported than Apple products; some big names were using ARM linux and raving about it.

It's still is a great laptop and I recommend it for the hardware overall, but not fan-less indeed.

reply
sharts
3 hours ago
[-]
Asahi is like a decade away from being 100% tho
reply
disdi89
1 hour ago
[-]
It is sad to see that they still do not support Snapdragon products with Linux offically as a product
reply
nullpoint420
1 hour ago
[-]
Just upstream your drivers! Then you don't need Qualcomm Linux.... you just have Linux.
reply
eschaton
1 hour ago
[-]
Why can’t upstream just take their drivers? Isn’t that the point of requiring those drivers to be GPL?
reply
zamadatix
1 hour ago
[-]
Imagine you wrote a WYSIWYG text editor, like Libre Office Writer. You have all sorts of functionality and an overall architecture which makes it sane to upkeep the project & have things work well together. Then someone else makes a custom font, but kind of does it their own way and with a different approach making it a one off from the way the rest of the fonts all work and are used in the program maybe using a custom font file format parser and different UI element even though you know it could have just used the normal, already maintained and planned out code paths.

You can of course merge anything with the right license if you so like, like that one off font code into your editor, but if it doesn't fit well into the overall project or meet the general quality standards of it then it's not practical to and can actually be worse than not including it. Upstreaming is about submitting something the maintainer can reasonably accept and maintain, not just about whether working code is available. GPL licensed code provides the latter, it's still up to someone (either the original company or some other interested person) to make it fit right first.

reply
wmf
41 minutes ago
[-]
Upstream requires a level of quality most developers cannot meet.
reply
realusername
19 minutes ago
[-]
The quality of the qcom code is way too low for upstream
reply
sipjca
1 hour ago
[-]
for real
reply
coredog64
2 hours ago
[-]
Recently bought an SBC with a QCS6490 (https://radxa.com/products/dragon/q6a/). Curious to see if the vendor winds up using this as a base.
reply
mrbluecoat
13 minutes ago
[-]
We'll see. They purposely dropped all server/console support and now only offer a Debian desktop image, which seems crazy for an SBC. Not exactly a welcome mat:

> Other variants that were previously provided AS-IS are no longer provided. Interested users need to build those by themselves.

https://github.com/radxa-build/radxa-dragon-q6a

AI / NPU use cases have been severely hampered as well:

https://gist.github.com/Foadsf/3cc2e0ed357c3ac7180589701bf83...

I've personally been wrestling with their broken I2C for a couple weeks.

Really want to love this board but lots of sharp edges at the moment. Hopefully Qualcomm keeps dedicating resources to improving things - I know it's hard work!

reply