From owner-freebsd-x11@freebsd.org Sun Apr 24 20:18:22 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 07A55B1B5E7 for ; Sun, 24 Apr 2016 20:18:22 +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-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EFB0110FD for ; Sun, 24 Apr 2016 20:18:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1461529094309773.7260583429751; Sun, 24 Apr 2016 13:18:14 -0700 (PDT) Date: Sun, 24 Apr 2016 13:18:14 -0700 From: Matthew Macy To: "freebsd-x11@freebsd.org" Message-ID: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> In-Reply-To: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> Subject: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps 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-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 24 Apr 2016 20:18:22 -0000 ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy wrote ---- > There seems to be some confusion about the state of drm-next-3.9. All the work is currently going on in jmd's fork of freebsd-base-graphics: > > https://github.com/iotamudelta/freebsd-base-graphics > > The emphasis has been on bringing i915 and the drm code in dev/drm2 closer to upstream as opposed to a simple driver refresh. I'm currently implementing missing linuxkpi bits and hope to actually be testing in the next week or so. > > As of this moment there is nothing available for general consumption. I very much hope to have this phase done before code freeze. I will update the list as soon as there is anything to test. Until then, hold your horses. > X now runs i915kms accelerated on the 3.9 driver update. Currently *only* SNA works. Known issues: - UXA will fail with: "(EE) failed to create screen resources(EE)". If someone has pointer on how to diagnose other than the usual trawling through Xorg sources let me know. - The module currently leaks memory on unload. My general feeling is that unless you have one of the half-dozen Haswell PCIIDS that aren't support by 3.8 it probably isn't worth testing yet. I'm only sending this out to let users track its progress. Cheers. -M