Date: Wed, 11 May 2016 02:29:36 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Update 2 the state of drm-next-4.6 and next steps Message-ID: <1549f266cc5.ea588cba219264.3594536435079440635@nextbsd.org> In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At least to some degree hw accelerated 3d works on the 4.6 i915 driver (which in principle supports up through Kaby lake - I don't yet have anything newer than Haswell). https://plus.google.com/114029301710423058970/posts/485LyZegC9B I anticipate maintaining all the pieces: linuxkpi, drm, i915, amdgpu, amdkfd as ports for the foreseeable future to make maintenance and continued development simpler. I hope to post a call for testers this weekend or early next week. Cheers. -M ---- On Sun, 24 Apr 2016 13:18:14 -0700 Matthew Macy <mmacy@nextbsd.org> wrote ---- > > > > ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy <mmacy@nextbsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1549f266cc5.ea588cba219264.3594536435079440635>