It seems like Valve and Collabora are working together to port Arch to ARM. They call it Holo Core which might be why the source code didn't show up but I think this is it probably?
Linux
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
I dont get it, I've been using Arch Arm for years on serveral Raspberry Pis. The hardware has to be supported but it works, and it's mantained
iirc the difference is that one is trying to port arch linux to arm and the other is trying to have arch linux run on arm without manual modification
Thank you for answering my question so succinctly haha
Arch doesn’t seem to have an ARM version
it's "unofficial" but arch has had an arm port for years: https://en.wikipedia.org/wiki/Arch_Linux_ARM / https://archlinuxarm.org/
where is the source code?
Steam has a bunch of code on the page you linked, including some Steam Frame-specific code. Note however that SteamOS is not an entirely free software (open source) operating system; it contains lots of free/libre software but also contains some proprietary parts. They are only required to ship source code for the copyleft-licensed components in it; nothing requires them to actually distribute a complete working distribution for hardware they don't want to. And, it appears that in the case of their ARM port, they do not currently distribute an image for anything besides their Frame device.
There was "Arch Linux ARM" ("ALARM") for a while but all updates that happen to it currently are automations. Stuff breaks more and more from time to time and the maintainer is unresponsive. I am assuming that's why the Asahi project moved to Fedora. And a new proposition inside of Arch Linux allows a "port" to be made but nobody submitted anything. It needs 2 maintainers minimum.
Anyways, so what I am assuming happened is that they just did their own port and never released the build scripts, because of course they would.
From what I've heard, only a small "base" is actually running natively and FEX has it's root set to a specific variant of the "Steam Linux Runtime" (you know, like when you install something on Steam it installs that?) fit to run Steam itself rather than games, but that's just my hypothesis.
Linux runs on a CPU which has an architecture, an internal set of rules and design guidelines. If you have a Linux kernel for an x86_64 processor it will work on any x86_64 processor, and the same goes for Arm. SteamOS can have two separate builds which target a different processor architecture but still have the same selection of tools and configuration to make a workable desktop experience. That is what they have done here.
Arm and x86_64 can both use WINE to run Windows applications on Linux, but on Arm systems we also need something similar to handle interpreting the x86_64 instructions to run correctly. That is something present in the Arm build that isn't in the x86_64 build. Also if you want to run Android apps on the Arm build you would need fewer layers for compatibility as the underlying instruction set matches, so you just need the operating system level things to make the app run properly.
Overall it is really simple conceptually but more complex practically. I am glad they are doing it, Arm is a much more power efficient architecture and is quite performant, so I am keen to see the results from here.
they use a translation layer