From owner-freebsd-current@freebsd.org Mon Feb 18 22:54:12 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 0384114EE7B1; Mon, 18 Feb 2019 22:54:12 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0750B89AE8; Mon, 18 Feb 2019 22:54:11 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id B719C17080; Mon, 18 Feb 2019 22:54:09 +0000 (UTC) Date: Mon, 18 Feb 2019 22:54:08 +0000 From: Mark Linimon To: "Rodney W. Grimes" Cc: Warner Losh , Baptiste Daroussin , Niclas Zeising , "freebsd-hackers@freebsd.org" , Stefan Blachmann , FreeBSD Current , Steve Kargl , Vladimir Kondratyev Subject: Re: What is evdev and autoloading? Message-ID: <20190218225407.GA7187@lonesome.com> References: <201902181650.x1IGoRsZ006131@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201902181650.x1IGoRsZ006131@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 0750B89AE8 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.74 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.86)[0.862,0]; IP_SCORE(-0.27)[ipnet: 18.220.0.0/14(0.06), asn: 16509(-1.34), country: US(-0.07)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.11)[0.106,0]; NEURAL_HAM_LONG(-0.65)[-0.646,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; RCPT_COUNT_SEVEN(0.00)[9]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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 22:54:12 -0000 On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote: > I think one serious problem here is the summary dismissal of things > simply on the "5 year old" basis. IIUC the graphics changes are being forced upon FreeBSD by external projects (mainly Linux-based) that are making huge architectural changes that rely more and more on features from newer hardware. If our upstreams aren't willing to do the work to keep from violating POLA on older hardware, IMHO it's an awful lot to ask of our already thinly stretched graphics volunteers to provide it in their stead. w/rt graphics, we are at far more danger of being left further and further behind on modern hardware than we are at risk of losing users on older hardware here. Again all IMHO. disclaimer: I don't use any fancy graphics stuff, so (as the old folks say around here) "I have no dog in this hunt". mcl