Date: Sun, 24 Apr 2016 14:25:52 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "cem@FreeBSD.org" <cem@FreeBSD.org> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps Message-ID: <1544a2a163d.b02b355958875.1610265201785479154@nextbsd.org> In-Reply-To: <CAG6CVpVx5nG1OPKzZJDjE47hOWbA9q4TxZn=dBraogK6NMOm8A@mail.gmail.com> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> <CAG6CVpVx5nG1OPKzZJDjE47hOWbA9q4TxZn=dBraogK6NMOm8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Sun, 24 Apr 2016 13:23:20 -0700 Conrad Meyer <cem@FreeBSD.org> wrote ---- > On Sun, Apr 24, 2016 at 1:18 PM, Matthew Macy <mmacy@nextbsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1544a2a163d.b02b355958875.1610265201785479154>