Heads up for breaking drm update.

[Johannes Lundberg]

On 5/19/19 7:36 PM, Steve Kargl wrote:
> On Sun, May 19, 2019 at 02:50:54PM -0700, Johannes Lundberg wrote:
>> LinuxKPI in base have received a lot of updates recently for Linux 5.0,
>> a couple of them will break drm-current-kmod. So, as of r347973 you will
>> need drm-current-kmod 4.16.g20190519. Ports have been updated and new
>> packages should be available shortly.
>>
> If drm-current-kmod is broken, should I venture to ask
> about drm-stable-kmod and drm-legacy-kmod?

That's a very good question. Maybe I should have included more
information regarding what's not affected. The last series of commits
have been to LinuxKPI in -CURRENT. As such:

drm-kmod: Meta port, not relevant
drm-current-kmod: See original message
drm-fbsd11.2-kmod: Not affected by changes in -CURRENT
drm-fbsd12.0-kmod: Not affected by changes in -CURRENT
drm-legacy-kmod: Not affected by changes in LinuxKPI

drm-stable-kmod does not exist anymore. Stable drm kmod ports for other
than -CURRENT are more or less frozen in separate branches where they
only receive bug fixes (drm-fbsdxxx-kmod).

Hope that answers your questions.

/Johannes


>