From owner-freebsd-x11@freebsd.org Mon May 21 17:29:57 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 67C05EFA530; Mon, 21 May 2018 17:29:57 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCB9168AC9; Mon, 21 May 2018 17:29:56 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.187] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e7e814d4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 21 May 2018 10:29:55 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu, Rozhuk Ivan Cc: Niclas Zeising , FreeBSD X11 mailing list , Current FreeBSD , Warner Losh , Oliver Pinter 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> <20180521170728.GA14025@troutmask.apl.washington.edu> From: Pete Wright Message-ID: Date: Mon, 21 May 2018 10:29:54 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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:29:57 -0000 On 05/21/2018 10:07, Steve Kargl wrote: > 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. to play devils advocate - why include a kernel module that causes conflicts for a vast majority of the laptop devices that you can purchase today (as well as for the foreseeable future), while forcing the up to date and actively developed driver to not work out of the box? IMHO it is issues like this (having out of date code that supports some edge cases) which makes it harder for developers to dog-food the actual OS they are developing on.  Having things work on modern hardware by default seems like a great way to get more people on the platform testing and bugfixing things. The suggestion seems like a pretty good middle ground, people with older devices will still have workable code while also making it easier to continue to follow the state of the art in terms of hardware support. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA