From owner-freebsd-x11@freebsd.org Sun Apr 24 21:25:55 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 512A4B1BA94 for ; Sun, 24 Apr 2016 21:25:55 +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 43C3A1835 for ; Sun, 24 Apr 2016 21:25:55 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1461533152881640.6638950935001; Sun, 24 Apr 2016 14:25:52 -0700 (PDT) Date: Sun, 24 Apr 2016 14:25:52 -0700 From: Matthew Macy To: "cem@FreeBSD.org" Cc: "freebsd-x11@freebsd.org" Message-ID: <1544a2a163d.b02b355958875.1610265201785479154@nextbsd.org> In-Reply-To: References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Subject: Re: 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 21:25:55 -0000 ---- On Sun, 24 Apr 2016 13:23:20 -0700 Conrad Meyer wrote ---- > On Sun, Apr 24, 2016 at 1:18 PM, Matthew Macy wrote: > > 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 pointers on how to diagnose other than the usual trawling > > through Xorg sources let me know. > > - The module currently leaks memory on unload. > > This might not even be a new issue (or: not a major regression). The > 3.8 driver leaked during unload when I tried it. > Good point. I have fewer issues when unloading 3.8, but it's certainly not without its issues. Seeing as the real gating factor on pushing these changes upstream is waiting on Jean to make the corresponding changes to update the radeon driver(s) I think I'll just move on to 4.6. Cheers. -M