From owner-freebsd-x11@freebsd.org Fri Aug 28 01:07:25 2020 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 BD0E33C86B2 for ; Fri, 28 Aug 2020 01:07:25 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4Bd1fP2MWvz3WTw for ; Fri, 28 Aug 2020 01:07:25 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: by mailman.nyi.freebsd.org (Postfix) id 4F2383C8730; Fri, 28 Aug 2020 01:07:25 +0000 (UTC) Delivered-To: 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 4DC8F3C87B0 for ; Fri, 28 Aug 2020 01:07:25 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bd1fN6zrmz3WfS for ; Fri, 28 Aug 2020 01:07:24 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 07S17PMI081926; Thu, 27 Aug 2020 18:07:31 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Thu, 27 Aug 2020 18:07:25 -0700 From: Chris To: Warner Losh Cc: FreeBSD X11 Subject: Re: deprecation of drm-legacy-kmod In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: <836d7a2f1f77a8d9c273a6935327924a@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Bd1fN6zrmz3WfS X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.33 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, 28 Aug 2020 01:07:25 -0000 On 2020-08-27 17:07, Warner Losh wrote: > On Thu, Aug 27, 2020 at 11:28 AM Chris wrote: > >> On 2020-08-24 15:21, Niclas Zeising wrote: >> > [ cross posted across several mailing lists, please respect reply-to ] >> > >> > Hi! >> > >> > It is time to deprecate drm-legacy-kmod, since it is taking too much >> time to >> > maintain and are holding off changes in other areas. >> > >> > drm-legacy-kmod was created to aid in the transition to the LinuxKPI >> based >> > graphics drivers, at a time when the new drivers only supported amd64. >> > Since >> > then, the new drivers have been updated to support more architectures >> and >> > more >> > GPUs, and the burden of maintaining drm-legacy-kmod has increased. It >> > became >> > apparent with the update of xorg-server to 1.20 that drm-legacy-kmod is >> too >> > old to >> > work with certain aspects of the graphics stack, and it is also holding >> back >> > changes in areas of the FreeBSD base system such as VM scaling and >> > optimization. >> > The VM locking protocol needs to be changed, and to port those changes >> to >> > these >> > drivers would require extensive reworking of its use of the FreeBSD VM >> > subsystem. >> > This means it is time for it to go. >> > >> > The driver will remain for a transition period. For FreeBSD 13-CURRENT, >> > this will >> > be fairly short, as there are changes to FreeBSD base that breaks the >> > drivers. >> > For FreeBSD 12, the driver will remain a bit longer, to ease in >> transition. >> > On >> > FreeBSD 12, there is also the option of using the graphics drivers in >> base, >> > although those are supported on a best-effort basis only. >> If this were pulled today. What are the ramifications? IOW what (A)GPUs >> would >> no longer be available for use on FreeBSD? Does one need to join a Linux >> Graphics >> list to find out what's currently supported? If so. What version of the >> Linux >> kernel? >> > > The ramifications are three fold. > > (1) There's some truly ancient graphics hardware that won't be supported > anymore. However they still work on stable 11 and stable 12. > (2) Improvements to the scaling of VM system can proceed forward. > (3) Efforts can be focused on the 5.4 Linux port that's in progress and > testing in -current. I was actually more concerned for what hardware would no longer be supported. That is; what (specific) hardware was now off the table as a result of this change. Not really a concern for my own hardware -- I stay relatively current. But rather for current, and future customers. I guess I just assumed that the "legacy" branch was specific to specific video cards, and processors, and that someone knew what they were. Thank you for taking the time to reply, Warner. --Chris > > For most people, though, this doesn't matter. It's not used by default and > you have to specifically opt into using it. > > Warner