From owner-freebsd-current@freebsd.org Tue May 22 22:47:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4387BEE4713 for ; Tue, 22 May 2018 22:47:18 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4DE76C881; Tue, 22 May 2018 22:47:17 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w4MMlFHe032111; Tue, 22 May 2018 15:47:15 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w4MMlFxm032110; Tue, 22 May 2018 15:47:15 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805222247.w4MMlFxm032110@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: To: "K. Macy" Date: Tue, 22 May 2018 15:47:15 -0700 (PDT) CC: "A. Wilcox" , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 22:47:18 -0000 > > 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. Are you saying there is only one way forward? -- Rod Grimes rgrimes@freebsd.org