From owner-freebsd-current@freebsd.org Mon Feb 18 16:45:42 2019 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 25A7514E2690; Mon, 18 Feb 2019 16:45:42 +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 5A5F270B25; Mon, 18 Feb 2019 16:45:41 +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 x1IGjdBe003116 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 18 Feb 2019 08:45:39 -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 x1IGjced003115; Mon, 18 Feb 2019 08:45:38 -0800 (PST) (envelope-from sgk) Date: Mon, 18 Feb 2019 08:45:38 -0800 From: Steve Kargl To: Warner Losh Cc: "Rodney W. Grimes" , Baptiste Daroussin , Niclas Zeising , "freebsd-hackers@freebsd.org" , Stefan Blachmann , FreeBSD Current , Vladimir Kondratyev Subject: Re: What is evdev and autoloading? Message-ID: <20190218164538.GB2912@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20190218155656.2mefeqixly6h25us@ivaldir.net> <201902181611.x1IGBQMD005946@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 5A5F270B25 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.98 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; TO_DN_SOME(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; 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_SEVEN(0.00)[8]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.08)[ip: (0.15), ipnet: 128.95.0.0/16(0.21), asn: 73(0.10), country: US(-0.07)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.83)[0.830,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[washington.edu]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.77)[0.772,0]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.61)[0.614,0]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 18 Feb 2019 16:45:42 -0000 On Mon, Feb 18, 2019 at 09:32:52AM -0700, Warner Losh wrote: > On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > So to ditch our 5 years support model, kick the code out of the tree and > > make the users suffer? The support model is suppose to be under review, > > and IMHO, if kicking functional code out of the base system is to make > > it possible to meet some support model we should defanitly take a very > > close look at that issue. > > > > The code has simply gone from being in base to a few git repositories > > which are probably going to rot every time a breaking ABI change occurs > > and we wend up with un happy users, un happy developers and bugmisters > > who have to close bogus bug reports. > > > > Have we really moved the state of the art forward by this action, simply > > in the name of "we could not suppor that code?" > > > > I don't know. I think the fact that drm2 doesn't support anything newer > than 5-year-old hardware is a pretty convincing evidence that the old way > is broken and doesn't work. > When drm2 was unhooked from the build, it was working fine. drm2 was unhooked because it supposedly interferred with the drm-stable-kmod and drm-current-kmod ports. -- Steve