There is currently work being done to get support for some snapdragon laptops into the kernel. I think 6.11 got preliminary support for a couple and patches for others are still waiting.
I am personally not exicted about using arm on pc/laptop all because situation with them can repwat situation with phones where we have locked down devices without ability to unlock bootloader and hug problems with drivers as sequence. Also there no uefi with ACPI so each distribution should be custom build to exact laptop because of operating system should know about installed hardware in laptop/pc in DTB file,i would prefer stay on x86 long as i can and maybe risc v cpus gonna change this situation.
Exactly. All the influencer hype and excitement over a locked down arm ecosystem with evaporating battery life advantages. No thank you. Development efforts are better served elsewhere. I would prefer the Linux community ignore it rather than support it at the expense of RISC-V.
Has Qualcomm ever been helpful?
I’m reading this on a bootloader locked S23U…while looking across the room I see my s10e,bootloader locked. And if I look in the distance my s7 is sitting there…locked…
I thought there were two units working now ( maybe not everything ). One Lenovo and one Asus if I recall.
EDIT:
ASUS Vivobook S15 & Lenovo Yoga Slim7x
https://www.phoronix.com/news/Linux-6.11-SoC-Platforms
6.11 is released now.
Qualcomm did work together with Microsoft and the Vendors closely together before the launch to create those devices.
Linux device vendors probably did not get the same treatment. So give it time. Also, why not buy a windows laptop and put linux on it?
Aren’t they arm-based? What’s the hurdle?
If the devs don’t have access to the hardware then it’s impossible to make drivers for a specific laptop
If it’s arm-based is the CPU so alien as to not being usable without a very generic kernel?
As for the hardware, is it so unique there are no drivers already?
ARM systems don’t have the whole ACPI thing to describe what hardware is where. Linux has to bodge together its view of the system with a devicetree instead. If you don’t know what device IP blocks are integrated into the SOC (and locked behind an NDA), good luck blindly guessing. You don’t even get EFI booting, you get shit like “the rpi gpu runs its own proprietary bootloader lol”.
I can’t speak for these specific laptops, but unlike x86, ARM generally doesn’t have a way for an OS to discover the available hardware, and most ARM platforms historically didn’t do anything to help. There is a standard for UEFI on ARM where the UEFI is supposed to tell the OS about the hardware, but as far as I know this is only a thing on ARM servers and these laptops might not support it.
Without any way of probing for hardware or getting the information from UEFI, Linux has to somehow be compiled with all the info about the hardware built-in. And the build will be model-specific (there’s a way to pass a file describing the hardware to Linux from the bootloader which enables a single kernel to be used on multiple models and have just a small part of the bootloader be model-specific, but somebody still needs to make that file and the manufacturers clearly don’t intend to do that).
Yep, an OS would need to be monolithic for a given device.
Something the computer world decided was a Bad Thing in about 1978.
Yes the drivers are all different afaik. You need a device tree, and hardware to debug what you wrote.
Just a kernel doesnt help much.
It would be cool if they provided at least a virtual machine to test on
Why a VM?
Because if they can’t provide them with real hardware at least a VM would be great
Like a VM emulating their exact hardware? Didnt know that was a thing
They have not seen the light
