61
Qualcomm goes where Apple won't, readies official Linux support for Snapdragon X Elite | Tom's Hardware
(www.tomshardware.com)
this post was submitted on 15 May 2024
61 points (100.0% liked)
Linux
48363 readers
560 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of the real downsides of ARM is, it seems, the relative lack of standardization. An x64 kernel? It'll run on most anything from the last ten years at least. And as for boot process, it's probably one of two options (and in many cases one computer can boot either legacy or EFI).
ARM, on the other hand...my raspberry pi collection does one thing, my Orange Pi does something else, and God help you if you want to try swapping the Orange kernel for the Raspberry (or vice versa)!
A standard called SystemReady exists. For the systems that actually follow its standards, you can have a single ARM OS installation image that you copy to a USB drive and can then boot through UEFI and run with no problems on an Ampere server, an NXP device, an Nvidia Jetson system, and more.
Unfortunately it's a pretty new standard, only since 2020, and Qualcomm in particular is a major holdout who hasn't been using it.
Just like x86, you still need the OS to have drivers for the particular device you're installing on, but this standard at least lets you have a unified image, and many ARM vendors have been getting better about upstreaming open-source drivers in the Linux kernel.
Arm:
Somehow, the kernel has been loaded and we have transferred control into it.
If the system is SystemReady then the EFI boot chain is fairly straightforward now. My current workstation just booted off the Debian usb installer like any other pc.
Faith in standards temporarily restored
i'm glad to find out this exists.
But we still need a hundred blobs and if the kernel needs to do something it has to make a call to the firmware.
This is what we get when you use Broadcom
Somehow, the kernel returned. -Poe dameron
“So far, Qualcomm has most of the critical functions working inside Linux, specifically version Linux 6.9 that was released not too long ago. These critical functions include UEFI-based boot support along with all the standard bootloaders like Grub and system-d.”
I'm hoping RISC-V will start showing up in consumer products soon. Hopefully the first ones will be Linux laptops. Windows doesn't have RISC-V support yet, does it? This might be the opportunity for Linux to become the default for RISC-V.
Anti Commercial-AI license
Sad android already dropped RISC-V support
Woah. Got a source for that?
Anti Commercial-AI license
https://hackaday.com/2024/05/03/google-removes-risc-v-support-from-android/
I think a lot of the problem is how proprietary some of the hardware is. For instance, the Raspberry pi only runs the raspberry pi kernel which has a lot of proprietary blobs.
Meanwhile boards from Pine64 don't need proprietary software to boot. The achieve this by being selective with the hardware and hardware vendors.
I don’t think this is as much of a problem, proprietary hardware is a thing on x86 too. The two big problems are a lack of boot standardization, and vendors not upstreaming their device drivers. A lack of standardization means it is difficult or impossible to use a single image to boot across different devices, and the lack of upstream drivers means even if you solved the boot process, you won’t be able to interface with peripherals without using a very custom kernel.
True, one of the issues of Android is also cost and development time. Manufacturers want to develop a product as cheap and fast as possible to keep up with demand.
That’s true for all commercial development. No company wants to invest more than they have to. Upstreaming does save time in the long run, but not in the short term.
Technically Google could of made upstreaming easier or even the default but they instead modified the kernel a bunch and then encouraged bad practices in development.
There are of course trade offs to everything though. For instance, Qualcomm could do better.