Date: Tue, 22 May 2018 15:19:44 -0700 From: "K. Macy" <kmacy@freebsd.org> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: "A. Wilcox" <AWilcox@wilcox-tech.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <CAHM0Q_M02heuWPBGv23C7OgiVYsMmMkqH6DjzyoUp1C0E-0-SQ@mail.gmail.com> In-Reply-To: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> References: <CAHM0Q_P0OAY3OHgMxZ0Ky6u2SKZOM8Q7uQLF5CuOjFRXTNRCFA@mail.gmail.com> <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I am concerned about just shoving it out to ports, as that makes > it rot even faster. > > I am still very concerned that our in base i9xx code is like 4 > years old and everyone is told to go to kmod-next from ports > as well. > > No, I do not have a solution, but I have not tried hard to find > one. I am sure if we try hard to find one it can be done. drm-next is a port and it's what most everyone will be using going forward. You're asking us to make a special case for a small vocal group of i386 users. If i386 is sufficiently important, its user base can support it. Cheers. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHM0Q_M02heuWPBGv23C7OgiVYsMmMkqH6DjzyoUp1C0E-0-SQ>