June 19, 2026 at 12:28 PM, "Bradley Morgan" <[email protected] mailto:[email protected]?to=%22Bradley%20Morgan%22%20%3Cinclude%40grrlz.net%3E > wrote:
> > On June 19, 2026 5:22:25 PM GMT+01:00, Sergey Bugaev <[email protected]> > wrote: > > > > > 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. > > > I already got a patch merged :) You've got one more code patch than I do! > > > > [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? > > > I'm personally experienced in bootloader development. You might be interested in Sergey's pet project. It's more about the OS bootstrap... https://hurd.ion.nu/open_issues/serverbootv2.html > Phones and androids are generally fun for me > > That transfers my knowledge over to arm32 (and 64) > > I hope we all can work together in closing in the arm port, and maybe > add more architectures as people start to migrate to hurd > > > > > > > > > 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 > > > Hmm, I see. But IMHO its slightly messy, to a new contributors eyes. > > That's why I suggested the arch directory > > If we like add more arches, then why not add a directory where all these > arches go > > > > > Sergey > > > Thanks! >
