Hi,
As far as I understand, the different types and versions of protection a
client would want is based on the resolution of the content, rather than
anything about what the content actually is. Is there any particular
reason a client would care if their content is being used on a higher
HDCP
On multi-GPU setups, multiple devices can be used for rendering. Clients need
hints about the device in use by the compositor. For instance, if they render
on another GPU, then they need to make sure the memory is accessible between
devices and that their buffers are not placed in hidden memory.
T
On Tue, 20 Nov 2018 20:32:53 +0800
zou lan wrote:
> Hi pekka
>
> Thank you so much to explain the drm backend details. I ask these because
> some company may implement their own drm backend, changes on interfaces
> between libweston
> and drm backend may increase the merge effort.
>
> Could I a
Hi pekka
Thank you so much to explain the drm backend details. I ask these because
some company may implement their own drm backend, changes on interfaces
between libweston
and drm backend may increase the merge effort.
Could I also ask is weston backward compatible from weston 2.0 to weston
5.0
On Tue, 20 Nov 2018 17:37:34 +0800
zou lan wrote:
> Hi pekka
>
> Thank you for your reply. I have other questions about drm backend.
> I find weston 5.0 modify so much about drm backend and the interfaces of
> compositor communicate with drm backend.
> Is there any documents about the drm backe
Hi pekka
Thank you for your reply. I have other questions about drm backend.
I find weston 5.0 modify so much about drm backend and the interfaces of
compositor communicate with drm backend.
Is there any documents about the drm backend design?
Why compositor need to add a structure weston_head? I
