Date: Sat, 13 Aug 2016 00:26:21 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Lundberg, Johannes" <johannes@brilliantservice.co.jp> Cc: "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: Wayland work status Message-ID: <15682cb6097.af30fe2f123452.8740060224087388607@nextbsd.org> In-Reply-To: <CAASDrVmDT=qEE7c5EU7nCntoipkP3CNfvEWCtRWVG_sF8rKiPg@mail.gmail.com> References: <CAASDrVmDT=qEE7c5EU7nCntoipkP3CNfvEWCtRWVG_sF8rKiPg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> > Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6 > branches. I'm working on this now for drm-next-4.6 and it is almost > complete. > I will probably implement it also in the 3.8 branch to be able to run > Wayland on both to compare and find bugs in linuxkpi more easily. Will > share patch for 3.8 branch when done. > drm-next has working kevent support following shortly after the drm-v4.7 tag. Your kqfilter implementation would be ideal for 3.8 but is not suitable for drm-next as it substantially modifies vendor code. I think your implementation does in fact work or is very close. Your apparent problem stemmed from an index overwrite in your modified kmscube.c test case. A working kmscube.c can be found at: https://github.com/FreeBSDDesktop/kmscube With no arguments it will use select. If you pass -k it will use kevent. -Mhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15682cb6097.af30fe2f123452.8740060224087388607>