Re: What is evdev and autoloading?

On Mon, Feb 18, 2019 at 09:32:52AM -0700, Warner Losh wrote:
> On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes <
> freebsd-rwg_at_pdx.rh.cn85.dnsmgr.net> wrote:
> 
> > So to ditch our 5 years support model, kick the code out of the tree and
> > make the users suffer?  The support model is suppose to be under review,
> > and IMHO, if kicking functional code out of the base system is to make
> > it possible to meet some support model we should defanitly take a very
> > close look at that issue.
> >
> > The code has simply gone from being in base to a few git repositories
> > which are probably going to rot every time a breaking ABI change occurs
> > and we wend up with un happy users, un happy developers and bugmisters
> > who have to close bogus bug reports.
> >
> > Have we really moved the state of the art forward by this action, simply
> > in the name of "we could not suppor that code?"
> >
> 
> I don't know. I think the fact that drm2 doesn't support anything newer
> than 5-year-old hardware is a pretty convincing evidence that the old way
> is broken and doesn't work.
> 

When drm2 was unhooked from the build, it was working fine.
drm2 was unhooked because it supposedly interferred with
the drm-stable-kmod and drm-current-kmod ports. 

-- 
Steve