Re: Introduction + interest in a riscv64 port of GNU Mach/Hurd

Santi cluke <[email protected]>
Newsgroups gmane.os.hurd.bugs
Message-ID <CAHr96OvvdmwHpPYSCS-k+9LBKXJtUp-ea05WCii0UOjLLcCv_A@mail.gmail.com>
Hi,

Thank you for the quick replies and the pointers.
Hakan, thanks for the stub port — it's a solid foundation to build on.
I've cloned your fork and will be replacing the stubs with working
implementations step by step.
Samuel, I'll check the bugaevc/wip-aarch64 branch for the multiboot
approach.
I'll send small patches as I go rather than sitting on a large branch.

Best,
Diego

El lun, 24 ago 2026 a la(s) 5:52 p.m., Hakan Candar (
[email protected]) escribió:

> Hi Diego,
>
> On Monday, 24 August 2026 at 23:40, Santi cluke <[email protected]>
> wrote:
>
> > Before starting, I wanted to ask about the state of Hakan Candar's
> riscv64
> > stub port from the April 2025 thread ("[RFC] riscv64 stub port for GNU
> Mach
> > – compiles, early WIP"). Is that work still active anywhere? I'd rather
> > build on it than duplicate the early groundwork.
> >
>
> > I'll send small patches as I go rather than sit on a large branch.
> Pointers
> > or warnings about dead ends are very welcome.
>
> Thanks for your interest. Please see the port at
>
> https://github.com/hakanrw/gnumach-riscv64.
>
> It's unfortunately still in the stub phase, just like in the
>
> post from April 2025. In fact, I have not made any improvements or
>
> additions after that...
>
> It should compile and link, but that's it. The next natural step would be
> to implement the boot routines, I think; and for that, we need a
>
> working implementation of multiboot for riscv. Sergey Bugaev has
>
> already implemented multiboot for aarch64, so we can check that as a
>
> guide.
>
> We should probably rebase it against upstream master, too.
>
> Been some time I wrote the stub port, so my knowledge of the code is
>
> quite foggy. I'd like to help you out if you have questions, though.
>
> Hakan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.