DRM removal soon

[Steve Kargl]

On Thu, Feb 28, 2019 at 10:49:51AM -0800, Cy Schubert wrote:
> On February 27, 2019 9:42:20 PM PST, Yoshihiro Ota <ota at j.email.ne.jp> wrote:
> >On Sun, 24 Feb 2019 10:24:15 -0700
> >Warner Losh <imp at bsdimp.com> wrote:
> >
> >> On Sun, Feb 24, 2019, 3:31 AM Yoshihiro Ota <ota at j.email.ne.jp>
> >wrote:
> >> 
> >> I also found that running kldstat was the easiest way to find which
> >of
> >> > driver to use instead of dmesg.
> >> >
> >> 
> >> Is this a suggestion for changing the drm-kmod package output? Or
> >just a
> >> helpful hint for others?
> >> 
> >> Tanks again.
> >> 
> >> Warner
> >
> >This is a helpful hint for others and a suggestion to update documents.
> >
> >I had read
> >https://www.freebsd.org/releases/12.0R/relnotes.html#hardware-graphics
> >and https://wiki.freebsd.org/Graphics before I started.  I had 4 old
> >laptops and 1 vmawre and I didn't remember which machine uses which CPU
> >:)
> >If the doc can mention to check kldstat output and go to corresponding
> >section, that will make steps easier.
> >
> >I converted to the port based driver for 4 psychical machines and 1
> >vmware machine (although vmware do not use neither of driver.)  All of
> >them run 12.0-RELEASE.  All of them start X and work fine.  I will
> >likely get to 13-CURRENT a lot later as I ran 13-CURRENT without X and
> >in vmware most of times.
> >
> >
> The ports work as advertised.  IMO graphics/drm-legacy should be
> depreciated sooner than later. I would expect the graphics team
> could better spend their time and energy on drm-current, which
> btw works perfectly on my old laptop converted to i386 testbed,
> than maintaining old bitrot. When can we expect drm-legacy to
> finally be removed from ports?
> 

drm-legacy-kmd has already been *depreciated*?

Perhaps, you meant deprecated.  :)

Hopefully, never.  drm-current-kmod locks up my laptop.
drm-legacy-kmod works.

-- 
Steve