search for: drm_prime_cap_local

Displaying 6 results from an estimated 6 matches for "drm_prime_cap_local".

2019 Apr 29
1
[Spice-devel] [PATCH] Revert "drm/qxl: drop prime import/export callbacks"
Hi, > > More useful would be some way to signal this self-reimport capability > > to userspace somehow. See DRM_PRIME_CAP_LOCAL patch. > > Userspace is supposed to test whether import/export works for a > specific combo, not blindly assume it does and then keel over. I think > we need to fix that, not add more flags - there's lots of reasons why > a given pair of devices can't share buffers (e.g. all...
2019 Apr 29
2
[Spice-devel] [PATCH] Revert "drm/qxl: drop prime import/export callbacks"
...Maybe we need some helpers for virtual drivers which only allow > self-reimport and nothing else at all? The current gem prime helpers handle this reasonable well, I don't see a need for that. More useful would be some way to signal this self-reimport capability to userspace somehow. See DRM_PRIME_CAP_LOCAL patch. Right now I have the choice to set DRM_PRIME_CAP_{IMPORT,EXPORT}, in which case some userspace assumes it can do cross-driver export/import and trips over that not working. Or I do not set DRM_PRIME_CAP_{IMPORT,EXPORT}, which breaks DRI3 ... > I think there's qxl, virgl, export is...
2019 Apr 29
2
[Spice-devel] [PATCH] Revert "drm/qxl: drop prime import/export callbacks"
...Maybe we need some helpers for virtual drivers which only allow > self-reimport and nothing else at all? The current gem prime helpers handle this reasonable well, I don't see a need for that. More useful would be some way to signal this self-reimport capability to userspace somehow. See DRM_PRIME_CAP_LOCAL patch. Right now I have the choice to set DRM_PRIME_CAP_{IMPORT,EXPORT}, in which case some userspace assumes it can do cross-driver export/import and trips over that not working. Or I do not set DRM_PRIME_CAP_{IMPORT,EXPORT}, which breaks DRI3 ... > I think there's qxl, virgl, export is...
2019 Apr 29
0
[Spice-devel] [PATCH] Revert "drm/qxl: drop prime import/export callbacks"
...irtual drivers which only allow > > self-reimport and nothing else at all? > > The current gem prime helpers handle this reasonable well, > I don't see a need for that. > > More useful would be some way to signal this self-reimport capability > to userspace somehow. See DRM_PRIME_CAP_LOCAL patch. Userspace is supposed to test whether import/export works for a specific combo, not blindly assume it does and then keel over. I think we need to fix that, not add more flags - there's lots of reasons why a given pair of devices can't share buffers (e.g. all the contiguous allocatio...
2019 Apr 26
3
[PATCH] Revert "drm/qxl: drop prime import/export callbacks"
This reverts commit f4c34b1e2a37d5676180901fa6ff188bcb6371f8. Simliar to commit a0cecc23cfcb Revert "drm/virtio: drop prime import/export callbacks". We have to do the same with qxl, for the same reasons (it breaks DRI3). Drop the WARN_ON_ONCE(). Fixes: f4c34b1e2a37d5676180901fa6ff188bcb6371f8 Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> ---
2019 Apr 26
3
[PATCH] Revert "drm/qxl: drop prime import/export callbacks"
This reverts commit f4c34b1e2a37d5676180901fa6ff188bcb6371f8. Simliar to commit a0cecc23cfcb Revert "drm/virtio: drop prime import/export callbacks". We have to do the same with qxl, for the same reasons (it breaks DRI3). Drop the WARN_ON_ONCE(). Fixes: f4c34b1e2a37d5676180901fa6ff188bcb6371f8 Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> ---