Summary: | media-libs/mesa with radeonsi/amdgpu should not require libdrm for radeon | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Klaus Kusche <klaus.kusche> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | dschridde+gentoobugs, nrndda |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Klaus Kusche
2019-10-12 12:29:51 UTC
> Most radeonsi cards use the amdgpu kernel driver and as far as I know
should need libdrm[video_cards_amdgpu] only, so libdrm[video_cards_radeon]
should *not* be set for them?
Key word: Most.
How do you suggest I differentiate between those that do require libdrm_radeon and those that don't? The upstream meson.build requires both libdrm_radeon and libdrm_amdgpu when the radeonsi driver is installed:
_libdrm_checks = [
['intel', with_dri_i915 or with_gallium_i915],
['amdgpu', with_amd_vk or with_gallium_radeonsi],
['radeon', (with_gallium_radeonsi or with_dri_r100 or with_dri_r200 or
with_gallium_r300 or with_gallium_r600)],
['nouveau', (with_gallium_nouveau or with_dri_nouveau)],
]
Even if it didn't, I wouldn't want to further complicate the configuration options for Mesa over a 50k shared object.
# ls -lh usr/lib*/libdrm_radeon.so.1.0.1
-rwxr-xr-x 1 root root 50K Oct 14 17:57 usr/lib64/libdrm_radeon.so.1.0.1
-rwxr-xr-x 1 root root 54K Oct 14 17:57 usr/lib/libdrm_radeon.so.1.0.1
(In reply to Matt Turner from comment #1) > Even if it didn't, I wouldn't want to further complicate the configuration > options for Mesa over a 50k shared object. I think the issue is more with USE-flag conflicts / missing USE-flags, when trying to emerge a system with VIDEO_CARDS=amdgpu set. In that case it is not immediately clear that, why and for which packages I need to also set VIDEO_CARDS=radeon. (In reply to Dennis Schridde from comment #2) > (In reply to Matt Turner from comment #1) > > Even if it didn't, I wouldn't want to further complicate the configuration > > options for Mesa over a 50k shared object. > > I think the issue is more with USE-flag conflicts / missing USE-flags, when > trying to emerge a system with VIDEO_CARDS=amdgpu set. In that case it is > not immediately clear that, why and for which packages I need to also set > VIDEO_CARDS=radeon. What do you suggest? (In reply to Matt Turner from comment #3) > (In reply to Dennis Schridde from comment #2) > > (In reply to Matt Turner from comment #1) > > > Even if it didn't, I wouldn't want to further complicate the configuration > > > options for Mesa over a 50k shared object. > > > > I think the issue is more with USE-flag conflicts / missing USE-flags, when > > trying to emerge a system with VIDEO_CARDS=amdgpu set. In that case it is > > not immediately clear that, why and for which packages I need to also set > > VIDEO_CARDS=radeon. > > What do you suggest? I have no good suggestion. But it would be nice, if I could just set VIDEO_CARDS=amdgpu once for my system and it would just work. Maybe make it an alias for VIDEO_CARDS=radeon in ebuilds that need it? |