graphics/drm-current-kmod: Update to drm_v5.4.62

[manu]

Summary

This update drm-current-kmod to be in sync with the latest Linux LTS
release.
aarch64 is also now supported for amdgpu and radeon.
vboxvideo is now added.

Sponsored-by: The FreeBSD Foundation
Signed-off-by: Emmanuel Vadot <[e-mail]>

[zeising]

One small nit above, nothing important.

As a side note, I wonder if we really should keep the SOURCE option enabled, it has caused issues in the past when people first do a buildkernel (with the old sources) and then update ports and think they have the new stuff, while still loading the old module built with buildkernel.

graphics/drm-current-kmod/pkg-plist

2

If you remove this from the plist, you probably want to remove the PLIST_SUB+=AMDKFD in the Makefile as well.

[zeising]

One more thing, can you update the version check in graphics/drm-kmod/Makefile as well?

[manu]

In D26367#586341, @zeising wrote:

One small nit above, nothing important.

As a side note, I wonder if we really should keep the SOURCE option enabled, it has caused issues in the past when people first do a buildkernel (with the old sources) and then update ports and think they have the new stuff, while still loading the old module built with buildkernel.

Well, installing the source will always causes problems when you update ports/package after building kernel but can help (sometimes) if nothing in base breaks building the module but it needs to be recompiled. It's the best solution that we have right now.

graphics/drm-current-kmod/pkg-plist

2

True, I'll update that.

[manu]

In D26367#586345, @zeising wrote:

One more thing, can you update the version check in graphics/drm-kmod/Makefile as well?

Good catch, I'll do that.

[zeising]

In D26367#586347, @manu wrote:

In D26367#586341, @zeising wrote:

One small nit above, nothing important.

As a side note, I wonder if we really should keep the SOURCE option enabled, it has caused issues in the past when people first do a buildkernel (with the old sources) and then update ports and think they have the new stuff, while still loading the old module built with buildkernel.

Well, installing the source will always causes problems when you update ports/package after building kernel but can help (sometimes) if nothing in base breaks building the module but it needs to be recompiled. It's the best solution that we have right now.

We've had several support cases where there's been confusion as to which module was loaded because of this. But this discussion is bigger than this review, and not something that should prevent the update from happening. :)

[manu]

In D26367#586352, @zeising wrote:

In D26367#586347, @manu wrote:

In D26367#586341, @zeising wrote:

One small nit above, nothing important.

As a side note, I wonder if we really should keep the SOURCE option enabled, it has caused issues in the past when people first do a buildkernel (with the old sources) and then update ports and think they have the new stuff, while still loading the old module built with buildkernel.

Well, installing the source will always causes problems when you update ports/package after building kernel but can help (sometimes) if nothing in base breaks building the module but it needs to be recompiled. It's the best solution that we have right now.

We've had several support cases where there's been confusion as to which module was loaded because of this. But this discussion is bigger than this review, and not something that should prevent the update from happening. :)

Oh yeah there was and will be a lot more confusion, I personnaly don't like this situation but as you said, the discussion is bigger than this review :)

[manu]

Address @zeising's comments.

[manu]

graphics/drm-kmod/Makefile

29

I've missed this one, will fix when commiting.

[zeising]

graphics/drm-kmod/Makefile

29

Sounds good. I didn't see it either until you pointed it out. :)