Linux

48328 readers

659 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

141

How is RISC-V better than arm for Linux? (programming.dev)

submitted 3 months ago* (last edited 3 months ago) by Timely_Jellyfish_2077@programming.dev to c/linux@lemmy.ml

43 comments fedilink hide all child comments

Help me understand this better.

From what I have read online, since arm just licenses their ISA and each vendor's CPU design can differ vastly from one another unlike x86 which is standard and only between amd and Intel. So the Linux support is hit or miss for arm CPUs and is dependent on vendor.

How is RISC-V better at this?. Now since it is open source, there may not be even some standard ISA like arm-v8. Isn't it even fragmented and harder to support all different type CPUs?

you are viewing a single comment's thread
view the rest of the comments

[–] HarriPotero@lemmy.world 5 points 3 months ago

I don't think there has been huge issues with incompatible ISAs on ARM. If you'd use NEON extensions, for example, you might have a C-implementation that does the same if the extensions are not available. Most people don't handwrite such code, but those that do usually go the extra mile. ARM SoCs usually have closed source drivers that cause headaches. As well as no standardized way of booting.

I haven't delved super-deep into RISC-V just yet, but as I understand these systems will do UEFI, solving the bootloader headache. And yes, there are optional extensions and you can even make your own. But the architecture takes height for implementing an those extensions in software. If you don't have the gates for your fancy vector instruction, you can provide instructions to replicate the same. It'll be slower on your hardware, but it'll be compatible if done right.