Linux support is still basically non-existent for the first gen, and they made all this deal about supporting Linux and the open source community. This is to say, don't trust them

▲

wyldfire 14 hours ago | parent | next [-]

The truth is much more subtle than "nonexistent" IMO [1].

Clearly it's a priority because the support for ChromeOS/android support is a big headline this year.

[1] https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdrag...

Also worth noting that not all the bits needing support are inside of the Snapdragon, so specific vendor support from Dell, Lenovo etc is required.

▲

wmf 14 hours ago | parent [-]

My (admittedly cynical) interpretation is that they are dropping support for desktop Linux completely and shipping Android drivers instead.

▲

cogman10 14 hours ago | parent | next [-]

That'd definitely fit the Qualcom pattern of trying to force you to update by not upstreaming their linux drivers.

This is one place where windows has an advantage over linux. Window's longterm support for device drivers is generally really good. A driver written for Vista is likely to run on 11.

	▲	packetlost 13 hours ago \| parent [-]
		A stable driver ABI will do that. And a couple billion in revenue to fund bending over backwards to make sure stuff doesn't break.

▲

tomComb 12 hours ago | parent | prev [-]

I thought “Android drivers” were Linux drivers?

▲

yjftsjthsd-h 12 hours ago | parent | next [-]

I think the situation is:

Old situation: "Android drivers" are technically Linux drivers in that they are drivers which are built for a specific, usually ancient, version of Linux with no effort to upstream, minimal effort to rebase against newer kernels, and such poor quality that there's a reason they're not upstreamed.

New situation: "Android drivers" are largely moved to userspace, which does have the benefit of allowing Google to give them a stable ABI so they might work against newer kernels with little to no porting effort. But now they're not really Linux drivers.

In neither case does it really help as much as you'd hope.

	▲	justincormack 4 hours ago \| parent [-]
		Old Android also had a bunch of weird kernel drivers that were not upstream; they mostly are now so Android kernel is converging on Linux finally.

▲

wmf 12 hours ago | parent | prev [-]

Android drivers don't support Wayland etc.

▲

cmxch 13 hours ago | parent | prev | next [-]

They “supported Linux” by putting it in a virtual machine guarded by the hardware against the machine’s owner. No thank you.

▲

eigenform 12 hours ago | parent | prev | next [-]

Not surprising considering I haven't seen a programming manual or actual datasheet for these things in the first place. Usually helps if you tell the community how to interact with your hardware ..

▲

wmf 12 hours ago | parent [-]

That ended 10-20 years ago. The best you can hope for now is vendor-provided drivers.

	▲	eigenform 9 hours ago \| parent [-]
		Not even true: Arm, Intel, AMD, and most other hardware vendors (who are actively making an effort to support Linux on their parts) actually publish useful[^1] documentation. edit: Also, not knocking the Qualcomm folks working on Linux here, just observing that the lack of hardware documentation doesn't exactly help reeling in contributors. [^1]: Maybe in some cases not as useful as it could be when bringing up some OS on hardware, but certainly better than nothing

▲

downrightmike 12 hours ago | parent | prev | next [-]

They expected linux devs to build it for free

	▲	yjftsjthsd-h 7 hours ago \| parent [-]
		In some cases the linux devs want to build it for free, but they still need enough information to work with

▲

cmrdporcupine 12 hours ago | parent | prev [-]

How's the WSL2 support on these Aarch64 Windows systems?

I'm not a huge fan of working in WSL, because I actively dislike the Windows GUI.

	▲	Mogzol 12 hours ago \| parent [-]
		I have both Ubuntu and Docker Desktop set up in WSL2 on my X Elite laptop, they both work great, no issues (at least none that I have run into).