From owner-freebsd-arch@freebsd.org Thu Feb 14 23:30:05 2019 Return-Path: Delivered-To: freebsd-arch@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 8115D14E6457 for ; Thu, 14 Feb 2019 23:30:05 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 04DB26B54F for ; Thu, 14 Feb 2019 23:30:03 +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 x1ENU0a8003427 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 14 Feb 2019 15:30:00 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x1ENU0LP003426; Thu, 14 Feb 2019 15:30:00 -0800 (PST) (envelope-from sgk) Date: Thu, 14 Feb 2019 15:30:00 -0800 From: Steve Kargl To: Warner Losh , "freebsd-arch@freebsd.org" Subject: Re: "DRM removal soon" is premature Message-ID: <20190214233000.GA2752@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20190214180101.GB67712@troutmask.apl.washington.edu> <20190214182419.GA67872@troutmask.apl.washington.edu> <20190214190244.GA68143@troutmask.apl.washington.edu> <20190214191739.GA68371@troutmask.apl.washington.edu> <20190214225810.kmfxzeuvr7t7gget@smtp.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190214225810.kmfxzeuvr7t7gget@smtp.freebsd.org> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 04DB26B54F X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.32 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.73)[0.734,0]; NEURAL_HAM_LONG(-0.46)[-0.465,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[washington.edu]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[21.76.95.128.list.dnswl.org : 127.0.11.2]; MX_GOOD(-0.01)[cached: troutmask.apl.washington.edu]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_MEDIUM(0.27)[0.274,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.09)[ip: (0.17), ipnet: 128.95.0.0/16(0.24), asn: 73(0.10), country: US(-0.07)] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2019 23:30:05 -0000 On Thu, Feb 14, 2019 at 02:58:10PM -0800, Ben Widawsky wrote: > > Not to pile on unnecessarily here, but I think the fundamental issue is that > there is nobody who wants to maintain the in-tree DRM, and removal is likely a > better option to half-assed maintenance. I'd imagine there'd be a different > discussion if several developers were clamoring to keep this driver well > maintained in the tree. > Unhooking a driver from the build, so that it cannot expose a change that breaks said driver is certainly a way to ensure the driver is not maintained. Wasted a weekend trying to find and attempting to fix the damage caused by a change in src/sys to the drm-legacy-kmod port. You know, the port that was promised as part of the drm2 removal. I would have spent this weekend testing changes to cexp, cexpf, the soon-to-be-submitted cexpl, ccosh, ccoshf, and the soon-to-be-submitted ccoshl. That's all on hold now as I'm not sure when I'll be able to carve out time for testing. -- Steve