Bring ARM into the fold?

[Rapty]

Hello
I'm referring to this subject from the x86 branch forum because, I think, @solskogen is also over here:make_clickable_callback(MAGIC_URL_FULL, '
', 'https://bbs.archlinux.org/viewtopic.php?pid=2291931#p2291931', '', ' class="postlink"')

I have dummy questions and sorry if it is well explained somewhere but on my side I'm still confused:
- what is the difference with the current aarch64 tgz ?
- Is the installation procedure the same we have here make_clickable_callback(MAGIC_URL_FULL, '(', 'https://archlinuxarm.org/platforms', '', ' class="postlink"'))
- will this new production create an linux-rpi version also ?

Thanks for the reply !
And of course, big thanks for the work for anyone for any branch anyway !

[technosf]

I think this speaks to how much ARM is moving into the desktop and server area that Arch are revisiting mainstreaming aarch64 etc.

A lot of good info in that discussion... I have great affection for ALARM and I would not like to see Arch railroad it, rather I think they need to understand the issues with supporting many many SoCs, but that ALARM should be educating them. ALARM should be educating it's own community too - this community is much diminished and it's heartbreaking. There is opportunity in a stronger relationship between Arch and ALARM for value in both directions.

ALARM can only survive if the people who use it are also brought into the fold and learn and are given a chance to contribute to ALARM, be it maintaining this, phyBB, documenting or designing processes, and ultimately maintains packages and managing builds. I've asked to be given a chance to give back but never a reply. What to do to reach someone and crack open the ALARM maintainer door to see a little light???

[solskogen]

The tarball we have can be installed the same way, yes. But with a few caveats: You have to install the kernel your self.
We are in the process of providing a installation image as well as a tarball. The installation image will come with pacstrap, so you'll just use the same method as upstream Arch. We aim to only support ARMv8.2-a and devices with UEFI (newer uboot provides this) - but with the exception of the Pi, we only have one kernel and we *aim* to keep it this way (when the Pi is supported in mainline, the linux-rpi kernel will go away)
Keep in mind that it will only work on Pi5/Pi500/Pi500+ and CM5.

Please note that this is a very very unofficial Arch Linux port as of now, but the goal is to bring it into upstream Arch. We're on Matrix and on #archlinux-ports on IRC if you want to chat!

[summers]

Isn't the thread linked and old tread (2 years). Yes some valid points made, but it doesn't change that it's old news. If nothing has changed in the last two years, why should it change now, e.g. What is different now?

[solskogen]

We're in progress, but it takes time. That said, we've have a hell of a lot more packages than ALARM. And pretty much up to date.