Date: Tue, 19 Feb 2019 08:31:47 -0700 From: Warner Losh <imp@bsdimp.com> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: Daniel Ebdrup <debdrup@gmail.com>, Oleksandr Tymoshenko <gonzo@bluezbox.com>, Michael Gmelin <grembo@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Niclas Zeising <zeising@freebsd.org>, Stefan Blachmann <sblachmann@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Mark Linimon <linimon@lonesome.com>, Vladimir Kondratyev <vladimir@kondratyev.su> Subject: Re: What is evdev and autoloading? Message-ID: <CANCZdfryLyEpn9DfuzgKYyo4T%2Bq1RjuXo=XQq7mca2oAgYhodQ@mail.gmail.com> In-Reply-To: <201902191425.x1JEPWAw010741@pdx.rh.CN85.dnsmgr.net> References: <77542747-D818-4A61-9D40-934A71D4EAEE@gmail.com> <201902191425.x1JEPWAw010741@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 19, 2019 at 8:17 AM Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > On 19 Feb 2019, at 09.15, Oleksandr Tymoshenko <gonzo@bluezbox.com> > wrote: > > > > > > Michael Gmelin (grembo@freebsd.org) wrote: > > >> > > >> > > >>>> On 18. Feb 2019, at 23:54, Mark Linimon <linimon@lonesome.com> > wrote: > > >>>> > > >>>> On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote: > > >>>> I think one serious problem here is the summary dismissal of things > > >>>> simply on the "5 year old" basis. > > >>> > > >>> IIUC the graphics changes are being forced upon FreeBSD by external > > >>> projects (mainly Linux-based) that are making huge architectural > changes > > >>> that rely more and more on features from newer hardware. > > The port was created long ago to get newer graphcis, that port even > had very nice instructions on how to bypass the inbase kmod of the > same name that accsesed the same hardware. > Yes. Those in-base drivers don't work. Or rather don't work well. The kinda sorta work for some people, but there's a huge number of kludges and hacks the graphics guys have been doing to keep it going and it's too much. Those hacks, like needing to make xf86-video-ati-legacy, like hacking back in support for drm2 in mesa which has moved on to requiring, basically drm3, like looking at issues that arise from there being regressions in drm-kmod on some older hardware. It's too much. There's lots of duct-tape and bailing wire that you don't see that's necessary to keep it going. That's the real bottom line here, whether you want to accept this harsh reality or not: we simply do not have the resources to continue to support drm2. I deleted the rest of your rant. It's not worth answering point by point. Things aren't like you think they are, and if the many polite (and not so polite) explanations haven't sunk in, another round sure won't help. drm2 is dead. The decision was made months ago. The game is finally over. I'll be committing the removal later today. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfryLyEpn9DfuzgKYyo4T%2Bq1RjuXo=XQq7mca2oAgYhodQ>