From owner-freebsd-x11@freebsd.org Fri Jan 29 11:34:46 2021 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A57E94E8509; Fri, 29 Jan 2021 11:34:46 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRwH94sCWz4mRV; Fri, 29 Jan 2021 11:34:45 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 857C5170FC; Fri, 29 Jan 2021 11:34:44 +0000 (UTC) Date: Fri, 29 Jan 2021 11:34:43 +0000 From: Mark Linimon To: Steve Kargl Cc: Emmanuel Vadot , freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: i915kms and chip resets on rsc0? Message-ID: <20210129113442.GA24082@lonesome.com> References: <20200710192736.GA69592@troutmask.apl.washington.edu> <20210128191510.GA96585@troutmask.apl.washington.edu> <20210128204806.77d1e676a592ec638a82d5be@bidouilliste.com> <20210128200255.GA96914@troutmask.apl.washington.edu> <20210128212213.a7e14bc4b469c745b522ea0a@bidouilliste.com> <20210128222040.GA97667@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210128222040.GA97667@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 4DRwH94sCWz4mRV X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of linimon@lonesome.com has no SPF policy when checking 18.222.6.11) smtp.mailfrom=linimon@lonesome.com X-Spamd-Result: default: False [0.96 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.84)[-0.845]; RCVD_IN_DNSWL_LOW(-0.10)[18.222.6.11:from]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[18.222.6.11:from]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[linimon]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[18.222.6.11:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-x11] X-Mailman-Approved-At: Fri, 29 Jan 2021 18:35:28 +0000 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 11:34:46 -0000 On Thu, Jan 28, 2021 at 02:20:40PM -0800, Steve Kargl wrote: > This is all likely academic as I just saw John Baldwin's email > that stated i386 support is being dropped in FreeBSD-current. s/dropped/downgraded/ The only difference seems to be that security upgrades that _only_ affect i386 will no longer be prioritized. This will put it mostly on a par with arm64, armv7, and powerpc64. That's all it means. mcl