From owner-freebsd-current@freebsd.org Sun May 22 08:14:26 2016 Return-Path: Delivered-To: freebsd-current@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 32B86B44654; Sun, 22 May 2016 08:14:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC8731DB3; Sun, 22 May 2016 08:14:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1b4OWe-0009ow-Ti; Sun, 22 May 2016 11:14:16 +0300 Date: Sun, 22 May 2016 11:14:16 +0300 From: Slawa Olhovchenkov To: Matthew Macy Cc: "freebsd-hackers@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported Message-ID: <20160522081416.GU1447@zxy.spb.ru> References: <154d75bfa01.110355533120837.2862753920701204888@nextbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <154d75bfa01.110355533120837.2862753920701204888@nextbsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 08:14:26 -0000 On Sun, May 22, 2016 at 12:26:49AM -0700, Matthew Macy wrote: > I'm happy to announce a call for testers for the 4.6 update of drm and > i915. The driver has been successfully tested on IvyBridge, Haswell, > Broadwell and Skylake. At least basic HW 3D acceleration should work, > VGA and DP out are known to work. Video decode has only been tried > once and that did not work. > > At this point I'm most interested in taking an inventory of what is > broken where. My priorities are common sense: > > a) stability > b) fixing 2D artifacts > c) fixing 3D problems > d) video decode > d) output support > e) other features > > At this time "prime" (needed for switching between GPUs, compute > APIs, and DRI3) is not yet supported. All the pieces are in place but > support existing functionality is a higher priority. Userptr (mapping > user memory in to the driver) requires VM changes. Support is > planned, but likely post-11. Can you do commit placeholder changes for VM for future MFC?