From owner-freebsd-x11@freebsd.org Mon Apr 25 13:15:28 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 A9E1AB1C3F6 for ; Mon, 25 Apr 2016 13:15:28 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 697E41168 for ; Mon, 25 Apr 2016 13:15:28 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1augMG-0005CF-FP; Mon, 25 Apr 2016 16:15:24 +0300 Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy , "freebsd-x11@freebsd.org" References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> From: Arto Pekkanen Message-ID: <571E1867.3070305@kapsi.fi> Date: Mon, 25 Apr 2016 16:15:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="j2X10tWLEJB4iKeEvHPokovFajp5etR7W" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false 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: Mon, 25 Apr 2016 13:15:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --j2X10tWLEJB4iKeEvHPokovFajp5etR7W Content-Type: multipart/mixed; boundary="TXjgdj27nwto9U9PJhujAfNr3xQAqEpva" From: Arto Pekkanen To: Matthew Macy , "freebsd-x11@freebsd.org" Message-ID: <571E1867.3070305@kapsi.fi> Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> --TXjgdj27nwto9U9PJhujAfNr3xQAqEpva Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thank you very much for the notice! It is always nice to receive updates on the situation of gfx drivers, since some people seem to be asking about these things ... so I can just ask them to subscribe to this mailing list ;D I haven't been using UXA since 10.1, SNA is stable enough nowadays. The only problem I have with SNA with 10.x is that enabling more than 2 outputs causes X.org to hang. With the updated driver from 3.8 this is no longer an issue :P On 24.04.2016 23:18, Matthew Macy wrote: >=20 >=20 >=20 > ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy wrote ----=20 > > There seems to be some confusion about the state of drm-next-3.9. Al= l the work is currently going on in jmd's fork of freebsd-base-graphics: > >=20 > > https://github.com/iotamudelta/freebsd-base-graphics > >=20 > > 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.=20 > >=20 > > As of this moment there is nothing available for general consumption= =2E I very much hope to have this phase done before code freeze. I will u= pdate the list as soon as there is anything to test. Until then, hold you= r horses. > >=20 >=20 > X now runs i915kms accelerated on the 3.9 driver update. Currently *onl= y* 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 t= rawling=20 > through Xorg sources let me know.=20 > - The module currently leaks memory on unload. >=20 >=20 > My general feeling is that unless you have one of the half-dozen Haswel= l 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. >=20 >=20 > Cheers. > -M >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --TXjgdj27nwto9U9PJhujAfNr3xQAqEpva-- --j2X10tWLEJB4iKeEvHPokovFajp5etR7W Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlceGGcACgkQTBivhqtJa26+AwEAhATGczVE3udSV61FKkW99BDw hn+ZR5w0sZhFf/rI80EA/1/2d8xBlJSoVi01XeKxmdrlNRvfOLB/3CCZJexGrF6a =9Atq -----END PGP SIGNATURE----- --j2X10tWLEJB4iKeEvHPokovFajp5etR7W--