From owner-freebsd-current@freebsd.org Tue May 22 23:36:10 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 92BCDEE5D65; Tue, 22 May 2018 23:36:10 +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 324726E06A; Tue, 22 May 2018 23:36:10 +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 w4MNZwTh097841 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 May 2018 16:35:58 -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 w4MNZwPn097840; Tue, 22 May 2018 16:35:58 -0700 (PDT) (envelope-from sgk) Date: Tue, 22 May 2018 16:35:58 -0700 From: Steve Kargl To: Johannes Lundberg Cc: Current FreeBSD , FreeBSD X11 mailing list , "K. Macy" , Niclas Zeising , Oliver Pinter , Rozhuk Ivan , Warner Losh Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522233558.GB97708@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) 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 23:36:10 -0000 On Tue, May 22, 2018 at 07:50:39AM +0100, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. > > > > Or why not include drm-next to base svn repo and add some > > > > option to make.conf to swith drm2/dem-next ? > > > > > > Even if it's not being built on amd64 we're still responsible for > > > keeping it building on !amd64 so long as it's in base. This makes > > > changing APIs and universe runs more burdensome. The graphics > > > developers have given you notice that it will now be your collective > > > responsibility to keep it up to date. > > > > > > > Not quite. One graphics developer has indicated a desire > > to remove working code, because it interferes with the > > graphics developers' port on a single architecture. There > > is no indication by that graphics developer that drm2 will > > be available in ports. You can go read the original post > > here: > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html > > > > The last paragraph is > > > > What does the community think? Is there anyone still using > > the drm2 driver on 12-CURRENT? If so, what is preventing > > you from switching to the port? > > > > The answer to the last two questions are "yes" and "the port > > does not work on i386". > > > > What is wrong with using > > > > .if ${MACHINE_ARCH} != amd64 > > ... > > .endif > > > > to enable/disable drm2? > > The answer to the first question is that the consensus seem to be that > moving to a port is best for the _majority_. Best for amd64. For the majority, if one starts X, it automatically loads drm2 if one allows X to configure itself and drm2 applies. It's automatically loaded on both by i386 laptop and amd64 desktop. > Let me ask you, what’s wrong with this one-liner after base install > pkg install drm2 > ? 1) The original email did not indicate the code would be moved to a port. It simply said removed. 2) Nothing wrong if you know where to go looking for drm2. FreeBSD goes from having drm2 automatically loaded for a user to hoping that a user knows about a port. 3) I've already posted a 2-line patch for amd64 (twice actually). How many lines are needed to make the port? -- Steve