Date: Mon, 18 Feb 2019 08:45:38 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Warner Losh <imp@bsdimp.com> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, Baptiste Daroussin <bapt@freebsd.org>, Niclas Zeising <zeising@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Stefan Blachmann <sblachmann@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org>, Vladimir Kondratyev <vladimir@kondratyev.su> Subject: Re: What is evdev and autoloading? Message-ID: <20190218164538.GB2912@troutmask.apl.washington.edu> In-Reply-To: <CANCZdfrEWX9jJVHUkFNijGpk9ii1H9PsUHtq=nD4M%2BnZacpCrQ@mail.gmail.com> References: <20190218155656.2mefeqixly6h25us@ivaldir.net> <201902181611.x1IGBQMD005946@pdx.rh.CN85.dnsmgr.net> <CANCZdfrEWX9jJVHUkFNijGpk9ii1H9PsUHtq=nD4M%2BnZacpCrQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190218164538.GB2912>