225
Schenker shows off a Linux laptop prototype with Snapdragon X Elite at Computex 2024
(liliputing.com)
this post was submitted on 03 Jun 2024
225 points (99.1% liked)
Linux
48338 readers
1021 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
What does that mean? Are they not using UEFI?
I just hope they use Coreboot.
Btw are there any FOSS Coreboot compatible ARM Chromebooks worth looking at?
Coreboot is for x86-64. ARM usually uses U-Boot.
Not true. For example Libreboot currently supports 2 ARM laptops. The way I understand it is that Libreboot uses U-boot as an extra bootloader, kinda like you would run GRUB after UEFI. U-boot can also just work on it's own and Coreboot ARM devices are rather the exception.
I'd argue chain loading coreboot/libreboot from u-boot isn't really "supporting it" as much as it's just extending it, but fair enough. In the end it's still using u-boot with extra steps.
Coreboot uses U-boot as payload meaning it's the other way around. (at least that's how I understand it) I worded poorly what I meant.
I never understood why booting arm is such a pain. I mean I get that the current situation is that it is a pain but I don't get why this is the situation.
Mobile devices usually run iOS or Android which have their own dedicated boot loader. Embedded devices usually just boot directly into the main storage.
Especially with android I don't get it. Every vendor has to maintain their own boot loader and modify the aosp code just to get it to boot on their devices. Is it just to avoid people slapping their own os on their phones?
Second one. Can't have user choice now can we
I think UEFI was something that took a while to be standardized and mostly because of Intel’s influence over it, while ARM seems more diverse both in manufacturers and types of devices. When things are decentralized it becomes much more difficult to get everyone on board of something.
I guess but bios was a thing way before uefi and while it apparently also was a pain because people implemented it differently it did work.
Afaik the mein problem with arm is the discoverability of the hardware on the bus. For x86 it's pretty dynamic but arm needs something called a device tree.