> From: Thomas Hellstrom
> Date: Wed, 23 May 2018 22:58:05 +0200
>
> On 05/23/2018 08:00 PM, Adam Jackson wrote:
> > On Wed, 2018-05-23 at 11:14 +0200, Thomas Hellstrom wrote:
> >> KMS drivers are not required to support GEM. In particular, vmwgfx
> >> doesn't support
On 05/23/2018 08:00 PM, Adam Jackson wrote:
On Wed, 2018-05-23 at 11:14 +0200, Thomas Hellstrom wrote:
KMS drivers are not required to support GEM. In particular, vmwgfx
doesn't support flink and handles and names are identical.
Getting a bo name should really be part of a lower level API, if
On Wed, 2018-05-23 at 11:14 +0200, Thomas Hellstrom wrote:
> KMS drivers are not required to support GEM. In particular, vmwgfx
> doesn't support flink and handles and names are identical.
> Getting a bo name should really be part of a lower level API, if needed,
> but in the mean time work around
On 23 May 2018 at 10:43, Michel Dänzer wrote:
> From: Michel Dänzer
>
> glamor_fds_from_pixmap returns 0 on error, but we were treating that as
> success, continuing with uninitialized stride and fd values.
>
> Also bail if the offset isn't 0, same as
On 05/23/2018 11:14 AM, Thomas Hellstrom wrote:
KMS drivers are not required to support GEM. In particular, vmwgfx
doesn't support flink and handles and names are identical.
Getting a bo name should really be part of a lower level API, if needed,
but in the mean time work around this by setting
From: Michel Dänzer
glamor_fds_from_pixmap returns 0 on error, but we were treating that as
success, continuing with uninitialized stride and fd values.
Also bail if the offset isn't 0, same as in dri3_fd_from_pixmap.
Fixes: c8c276c9569b "glamor: Implement
From: Michel Dänzer
This matches what glamor_egl_fds_from_pixmap and dri3_fds_from_pixmap do
and what proc_dri3_buffers_from_pixmap expects.
Fixes: c8c276c9569b "glamor: Implement PixmapFromBuffers and
BuffersFromPixmap"
Signed-off-by: Michel Dänzer
KMS drivers are not required to support GEM. In particular, vmwgfx
doesn't support flink and handles and names are identical.
Getting a bo name should really be part of a lower level API, if needed,
but in the mean time work around this by setting the name identical to
the handle if GEM isn't