"DRM removal soon" is premature
Steve Kargl
sgk at troutmask.apl.washington.edu
Thu Feb 14 19:02:49 UTC 2019
On Thu, Feb 14, 2019 at 11:51:41AM -0700, Warner Losh wrote:
> On Thu, Feb 14, 2019 at 11:24 AM Steve Kargl <
> sgk at troutmask.apl.washington.edu> wrote:
>
> > On Thu, Feb 14, 2019 at 11:08:18AM -0700, Warner Losh wrote:
> > > On Thu, Feb 14, 2019 at 11:01 AM Steve Kargl <
>
> > In your original post (which I cannot respond
> > to as I came too late to freebsd-arch), you wrote
> >
> > Since the drm-legacy-kmod or the drm-kmod packages seem to be
> > stable and working well for most people, the time has come to
> > finish the removal of most of the drm code in FreeBSD.
> >
> > I'm pointing out the fallacy of that statement for anyone
> > running freebsd-current on i386 who uses drm-legacy-kmod.
> >
>
> Hence my qualification of "most people" :)
>
> > Niclas proposed a fixed for drm-legacy-kmod here
> >
> > https://lists.freebsd.org/pipermail/freebsd-x11/2019-February/022759.html
> >
> > I reported on testing his proposed fix here
> >
> > https://lists.freebsd.org/pipermail/freebsd-x11/2019-February/022760.html
> >
> > and here
> >
> > https://lists.freebsd.org/pipermail/freebsd-x11/2019-February/022762.html
>
> You might try this fix instead, though I don't think it will matter. I
> think the breakage you're seeing is a result of a subtle dependency in the
> drm2/ttm code with FreeBSD's vm system. Even had it been connected to the
> build and fixed at the time, I don't think it would have mattered.
>
I can't test the patch for several hours, and it will take
6 to 7 hours to rebuild world/kernel. So, I'll have to report
back tomorrow.
--
Steve
More information about the freebsd-arch
mailing list