Re: libdrm+kernel patches/fixes from wayland porting work
Jeff Frasca <[email protected]> Sat, 1 Feb 2025 14:24:48 -0800
| Newsgroups | gmane.os.netbsd.devel.x11 |
|---|---|
| Message-ID | <CAOyJ0LnCiXC5FsqyKhDja+qBdj1+_zixTL5E2NHWAmz_v0Da9w@mail.gmail.com> |
On Thu, Jan 30, 2025 at 11:32=E2=80=AFPM Taylor R Campbell <riastradh@netbs= d.org> wrote: > > > Date: Thu, 30 Jan 2025 23:13:45 -0800 > > From: Jeff Frasca <[email protected]> > > Last year I made some changes to HEAD to address this: > > PR kern/58180: render nodes are busted https://gnats.NetBSD.org/58180 > https://mail-index.NetBSD.org/source-changes/2024/04/21/msg150921.html > https://mail-index.NetBSD.org/source-changes/2024/04/21/msg150922.html > > The approach was to pass the same information through the GET_UNIQUE > ioctl and expose it to render nodes. > > However, that exposed some other bug which broke Firefox or something, > so it's not getting pulled up to 10. > > Will take a look at the rest later when I have a moment! I just looked at your change to drm_getunique, and not only does that look like a totally reasonable solution to the problem I was having, my compositor starts up just fine with stock kernel, MesaLib from pkgsrc and stock libdrm. Forget my patches. NetBSD-current is good. And I can pull this down for personal use if I want to run release code (which I will probably do for my bare metal install and one of my dev VMs). That said, I've still got stuff to work on here, as it does not cleanly shut down (something that works fine on Linux and OpenBSD). Instead, the screen blanks and my fans spin up. The machine hasn't hung or panicked, as I can still do a clean shutdown via SSH. I will dig more on that front. Jeff