Date: Thu, 14 Feb 2019 10:24:19 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: "DRM removal soon" is premature Message-ID: <20190214182419.GA67872@troutmask.apl.washington.edu> In-Reply-To: <CANCZdfqy%2Bs3QtEu%2BAhTm-HoJfByjeA9EeUGZ_3VrThvrcWvBow@mail.gmail.com> References: <20190214180101.GB67712@troutmask.apl.washington.edu> <CANCZdfqy%2Bs3QtEu%2BAhTm-HoJfByjeA9EeUGZ_3VrThvrcWvBow@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 14, 2019 at 11:08:18AM -0700, Warner Losh wrote: > On Thu, Feb 14, 2019 at 11:01 AM Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > Warner, > > > > I'm not subscribed to freebsd-arch (well I am now!) > > > > drm-legacy-kmod is broken on i386-*-freebsd due > > to r343567. I posted about this issue in > > freebsd-current, freebsd-x11 lists. Find yourself > > a post r343567 system, build drm-legacy-kmod, and > > xorg and see what happens. > > > > > > https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072802.html > > https://lists.freebsd.org/pipermail/freebsd-x11/2019-February/022754.html > > > The in-tree versions don't even compile, how are they better than the > drm-legacy-kmod modules which do, but don't work for some people (and do > for others)? > The in-tree version does not compile because someone disconnected drm2 from the build. r342567 would not have happen if drm2 was not disconnected. 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. 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 -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190214182419.GA67872>