From owner-freebsd-current@freebsd.org Mon Aug 17 18:44:43 2020 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 BC17E3B97A8; Mon, 17 Aug 2020 18:44:43 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BVjdR4fkDz44lB; Mon, 17 Aug 2020 18:44:43 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 88070156F9; Mon, 17 Aug 2020 18:44:43 +0000 (UTC) From: Jan Beich To: Emmanuel Vadot Cc: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: DRM Project report (week of August 10) References: <20200817104608.d29dc8834ccc93c18b884a29@bidouilliste.com> Date: Mon, 17 Aug 2020 20:44:38 +0200 In-Reply-To: <20200817104608.d29dc8834ccc93c18b884a29@bidouilliste.com> (Emmanuel Vadot's message of "Mon, 17 Aug 2020 10:46:08 +0200") Message-ID: <4kp1-5cyx-wny@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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, 17 Aug 2020 18:44:43 -0000 Emmanuel Vadot writes: > Hello, > > 5.4 was finilly reached ! > For AMD users it means that Navi12/14, Arctarus and Renoir should work. > For Intel users it means that TigerLake should work too. > > No ports update for now as I want to give current users a bit of time > to update their base (as the ports needs recent addition to > base linuxkpi) but if you have a current >= 364233 you can test > directly the master branch of https://github.com/freebsd/drm-kmod/ > > I plan to commit the port update at the end of the week, and probably > at the end of the month we will switch drm-current-kmod to 5.4. > > It's now time to do 2 main things : > - Update stable/12 so it have all the needed code to run 5.4 > - Remove the remaining GPLv2 code to start thinking of import into > base. Upstream v5.4 was tagged on 2019-11-24. Did you check linux-5.4.y (LTS) doesn't require more LinuxKPI changes? For example, when drm-v5.0 was the latest I've played with grafting linux-4.19.y only to discover some commits had to be reverted due to missing LinuxKPI bits.