Date: Sun, 14 Aug 2016 17:55:57 +0200 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor <listjm@club.fr> To: "<freebsd-x11@freebsd.org>" <freebsd-x11@freebsd.org>, Matthew Macy <mmacy@nextbsd.org> Subject: drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged Message-ID: <57B0948D.9010502@club.fr>
next in thread | raw e-mail | index | archive | help
> I have merged up through v4.7 and fixed a number of issues. I've also added kevent support to drm and merged in evdev, so all the kernel dependencies for Wayland are enabled by default in GENERIC. I've tagged the last commit as drm-v4.7-final as following that I will start merging v4.8-rc1 changes. > > With the final change Wayland now works on post-Haswell hardware: > https://twitter.com/Yohanesu75Tweet/status/764640489429540864 > > Unfortunately I still see corruption when playing multiple videos on chrome (chrome has hardware accelerated video playback). FF (not offloaded) does not show corruption, but requires the use of a compositor to avoid tearing to keep frame updates in sync with screen refresh. > > The scope of my personal testing is limited so please report any regressions with respect to drm-next-4.6. No regressions here with drm-4.7-final. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57B0948D.9010502>