Date: Sat, 21 Dec 2019 20:54:14 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: r355978 OK (was: SVN r355732 breaks DRM) Message-ID: <20ecabfd-91fd-9b03-a208-7b9876c2764a@gmail.com> In-Reply-To: <e94fabaf-f617-41cf-90f1-bb9bc26e3b18@yggdrasil.evilham.com> References: <79d0207a-994b-4c79-fa80-ef1c58078b77@protected-networks.net> <CANCZdfpKHVQKgTqFyyS9jB6FqsBsFJq-x4R9ywRggP6CuSi9tA@mail.gmail.com> <28378fc6-8811-8431-b7d0-87474e1b11b2@gmail.com> <e94fabaf-f617-41cf-90f1-bb9bc26e3b18@yggdrasil.evilham.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/12/2019 10:21, Evilham wrote: > > On dc., des. 18 2019, Graham Perrin wrote: > >> On 14/12/2019 01:30, Warner Losh wrote: >> >> > A fix is in progress. >> >> Thank you. >> >> r355860 drm-legacy-kmod <https://pastebin.com/NcrA9iLe>; lines 70–81: the >> same issue, yes? > > FWIW: https://github.com/FreeBSDDesktop/kms-drm/issues/198 > > I've been using a locally built drm-kmod without patches (off commit > ee53eae) for a couple days with the latest HEAD. > Maybe the port just hasn't been rebuilt on FreeBSD infra yet? > > In any case, and at your own risk you can give that a go. > -- > Evilham Thank you. All good with what's above and r355978.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20ecabfd-91fd-9b03-a208-7b9876c2764a>