From owner-freebsd-current@freebsd.org Wed Dec 18 10:21:56 2019 Return-Path: Delivered-To: freebsd-current@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 B41051DAF19 for ; Wed, 18 Dec 2019 10:21:56 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47d9zR5ZVsz4QvG for ; Wed, 18 Dec 2019 10:21:55 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 47d9zH56qFz3wf3; Wed, 18 Dec 2019 11:21:47 +0100 (CET) From: Evilham To: Graham Perrin Cc: freebsd-current@freebsd.org Subject: Re: SVN r355732 breaks DRM References: <79d0207a-994b-4c79-fa80-ef1c58078b77@protected-networks.net> <28378fc6-8811-8431-b7d0-87474e1b11b2@gmail.com> In-reply-to: <28378fc6-8811-8431-b7d0-87474e1b11b2@gmail.com> Date: Wed, 18 Dec 2019 11:21:44 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47d9zR5ZVsz4QvG X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-6.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-3.68)[ip: (-9.86), ipnet: 46.19.32.0/21(-4.93), asn: 196752(-3.66), country: NL(0.03)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(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: Wed, 18 Dec 2019 10:21:56 -0000 On dc., des. 18 2019, Graham Perrin wrote: > On 14/12/2019 01:30, Warner Losh wrote: > > > A fix is in progress. > > Thank you. > > r355860 drm-legacy-kmod lines=20 > 70=E2=80=9381: the > same issue, yes? FWIW: https://github.com/FreeBSDDesktop/kms-drm/issues/198 I've been using a locally built drm-kmod without patches (off=20 commit ee53eae) for a couple days with the latest HEAD. Maybe the port just hasn't been rebuilt on FreeBSD infra yet? In any case, and at your own risk you can give that a go. -- Evilham