From owner-freebsd-x11@freebsd.org Mon May 21 17:07:48 2018 Return-Path: Delivered-To: freebsd-x11@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 F2578EF8F50; Mon, 21 May 2018 17:07:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8126587467; Mon, 21 May 2018 17:07:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4LH7TRL014115 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 21 May 2018 10:07:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4LH7StF014114; Mon, 21 May 2018 10:07:28 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 May 2018 10:07:28 -0700 From: Steve Kargl To: Rozhuk Ivan Cc: Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521170728.GA14025@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180521024050.0857a787@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2018 17:07:48 -0000 On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > On Sun, 20 May 2018 21:10:28 +0200 > Oliver Pinter wrote: > > > > One of the reasons for the deprecation and removal of the drm2 bits > > > is that they prevent us from automatically loading the > > > drm-next/stable-kmod kernel modules, since the two collide. > > > Regards > > > > > > Then it wold be better to resolve this problem, rather then removing a > > working solution. What's about module versioning what in other cases > > works? > > > > May be just move old drm2 to ports? Why? "If it isn't broken, why fix it?" The conflict affects x86_64-*-freebsd aka amd64. The conflict does not affect any other architecture. The Makefile infrastructure can use MACHINE_ARCH to exclude drm2 from build of amd64. I don't use netgraph or any of the if_*.ko modules. Can we put all of that into ports? I don't use any scsi controllers, so those can go too. Why make it insanely fun for users to configure a FreeBSD system. -- Steve