From owner-freebsd-x11@freebsd.org Sun Aug 14 02:57:59 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DB02BB812A; Sun, 14 Aug 2016 02:57:59 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 378A717CB; Sun, 14 Aug 2016 02:57:58 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1471143476998425.02494601166813; Sat, 13 Aug 2016 19:57:56 -0700 (PDT) Date: Sat, 13 Aug 2016 19:57:56 -0700 From: Matthew Macy To: "Matthew Macy" Cc: "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <15686fbfed7.b47b2120143737.5219243845741262240@nextbsd.org> In-Reply-To: <1567da024af.bfcdfbc455906.5120985150976586422@nextbsd.org> References: <1567da024af.bfcdfbc455906.5120985150976586422@nextbsd.org> Subject: drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-ZohoMail: Z_57973067 SPT_1 Z_57973066 SPT_1 SLF_D X-Zoho-Virus-Status: 2 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2016 02:57:59 -0000 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. ---- On Fri, 12 Aug 2016 00:21:02 -0700 Matthew Macy wrote ---- > > A few days ago I branched drm-next-4.6 in to drm-next and synced it with Torvalds' tree as of the v4.6 tag. I then integrated the ~800 commits to drm / i915 / radeon / amdgpu , testing periodically along the way and updating the linuxkpi as needed. I've just tagged the drm-next branch with drm-4.7-rc1 to indicate that it is in sync with 4.7-rc1 upstream. > > If any of you are feeling adventurous I would appreciate it if you would try it and report any regressions with respect to drm-next-4.6. I'm aware that there are a number of issues with drm-next-4.6 so I'm only really interested in _new_ issues. > > If you're feeling really adventurous - run the piglit test suite from the ports' xserver-next branch and do a root cause analysis on test failures. > > As always the repo is at: > https://github.com/FreeBSDDesktop/freebsd-base-graphics > > Look through the existing open issues before filing a report and check the wiki first to address any problems. > > Cheers. > > -M > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >