On Fri, Jun 19, 2026 at 1:27 AM include <[email protected]> wrote: > On June 18, 2026 11:13:47 PM GMT+01:00, Diego Nieto Cid <[email protected]> > >El jue, 18 jun 2026 a las 18:37, include (<[email protected]>) escribió: > > > >> Question, is ARM64 supported, if not, no worries, I'll add it. > >> > >> > >Sergey started porting GNU Hurd to aarch64[1] and there have been some > >more > >recent attempts at polishing the patches by Paulo[2]. You may search the > >mailing list from its archive page in case I missed something relevant[3].
Indeed, I was hacking on the AArhc64 port (aarch64-gnu) in 2024. It was working somewhat, but not anywhere nearly as complete/usable as the x86 ports. If you are entirely unfamiliar with the Hurd, I suggest you grab an x86_64 GNU/Hurd system (Debian GNU/Hurd is the easiest) and explore it for a while before looking at the AArch64 port. [0] gives a more recent update (compared to the initial announcement) on the state of that aarch64-gnu, and [1] might also be relevant, in the bit about drivers and interrupts. [0]: https://lists.nongnu.org/archive/html/bug-hurd/2024-03/msg00114.html [1]: https://lists.nongnu.org/archive/html/bug-hurd/2026-05/msg00044.html What are you experienced in? What sort of projects have you worked on? > Looks fun, heh. > > maybe architecture related code should be in arch/? > > instead of aarch64/ > > otherwise it'll be a mess, lol > > riscv/ mips/ x86/ etc, That is a small detail in the grand scheme of things... perhaps an arch/ directory would be more clear, but Mach historically always had per-architecture ports at the top level. See alpha/, i386*/, mips/ at [2] for example. [2]: https://github.com/Prajna/mach/tree/master/kernel Sergey
