Date: Mon, 17 Aug 2020 20:44:38 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: DRM Project report (week of August 10) Message-ID: <4kp1-5cyx-wny@FreeBSD.org> In-Reply-To: <20200817104608.d29dc8834ccc93c18b884a29@bidouilliste.com> (Emmanuel Vadot's message of "Mon, 17 Aug 2020 10:46:08 %2B0200") References: <20200817104608.d29dc8834ccc93c18b884a29@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Emmanuel Vadot <manu@bidouilliste.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4kp1-5cyx-wny>