Hi Damien, How does the graphics system work today on Hurd? DRM is not strictly needed to run Wayland, we can get away with software rendering to fb (not many compositors support this these days), We can also run Wayland on X to get started. I was wondering if it’s a good idea to start port everything but DRM to get something working. I assume there is no epoll? If not we can do something like *bsd are doing with epoll-shim.
Marius Gripsgard On 12/11/2025 04:40, Damien Zammit wrote: > Hi Marius, > > We need to port kms and drm server from the Linux kernel as a userspace > translator that implements the DRM ioctl api so that libdrm can plug into it. > > But its easier said than done because there are virtual addresses being > passed in the ioctl apis that won't resolve between different processes, as I > understand. The suggestion was to implement some of the ioctls in glibc > directly so the addresses would be resolvable in the client. I made a start > on the drm RPCs in my Hurd fork here [1] but there are over 200 of them. If > you have knowledge of Wayland it would be useful if you could write a list of > strictly essential DRM calls that are needed to run a Wayland desktop so we > can focus on just implementing those. > > Damien > > [1] https://git.zammit.org/hurd-sv.git/log/?h=drm-server-ioctl > > Sent from Proton Mail Android > > > > -------- Original Message -------- > On 12/11/25 12:35 pm, Marius Gripsgard wrote: > Hey all, > > I am interested in helping out to try to get some sort of Wayland working on > Hurd. I have long experience with Wayland (and its components) on Linux and > know Linux graphics well. How does this translate to Hurd? What does Hurd use > to render, etc.? Does Hurd use OpenGL, etc.? I know X11 is working on Hurd, > how is that implemented? I'll try searching the source myself, but please, if > you have any pointers that can help. > > > > On a side note, i'm a debian DD, so i'll try my best to port my packages that > fail also. > > > > Best, Marius Gripsgard
