libdrm_amdgpu being forked and merged into Mesa
Bas Nieuwenhuizen
bas at basnieuwenhuizen.nl
Fri Oct 25 17:07:19 UTC 2024
On Fri, Oct 25, 2024 at 6:57 PM Michel Dänzer <michel.daenzer at mailbox.org>
wrote:
> On 2024-10-25 17:57, Bas Nieuwenhuizen wrote:
> > On Fri, Oct 25, 2024 at 4:36 PM Michel Dänzer <
> michel.daenzer at mailbox.org <mailto:michel.daenzer at mailbox.org>> wrote:
> > On 2024-10-25 12:18, Bas Nieuwenhuizen wrote:
> >
> > > (not to mention that it would mean that any users would need to
> use libdrm_amdgpu. Given that the most likely combination of GBM with
> shared fd/handle stuff is kernel modesetting and nobody uses libdrm_amdgpu
> with that, having a shared libdrm_amdgpu would not help there)
> >
> > Not sure what you mean here, Wayland compositors use radeonsi with
> KMS.
> >
> > That is what I mean, since they use KMS directly, anything that radeonsi
> does wrt using or not using libdrm_amdgpu doesn't impact them.
>
> Still not following. Wayland compositors generally use the same DRM file
> description for radeonsi (via the EGL GBM platform) and KMS.
>
And they will after this change, i.e. this is not a problem wrt this
change.
>
>
> > (note that some compositors, like gamescope do the actual dmabuf dance
>
> AFAIK gamescope uses Vulkan, not GL.
>
>
> --
> Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
> https://redhat.com \ Libre software enthusiast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20241025/53846999/attachment-0001.htm>
More information about the mesa-dev
mailing list