Date: Tue, 18 Aug 2020 10:25:10 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Jan Beich <jbeich@FreeBSD.org> Cc: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: DRM Project report (week of August 10) Message-ID: <20200818102510.483dabc30639d4d7b20ed17e@bidouilliste.com> In-Reply-To: <4kp1-5cyx-wny@FreeBSD.org> References: <20200817104608.d29dc8834ccc93c18b884a29@bidouilliste.com> <4kp1-5cyx-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Aug 2020 20:44:38 +0200 Jan Beich <jbeich@FreeBSD.org> wrote: > 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. Not yet, but those bits could be added in the ports for 12.2 if they are needed anyway. -- Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200818102510.483dabc30639d4d7b20ed17e>