On Wed, Apr 10, 2019 at 12:40 PM Simon Ser wrote:
> On Wednesday, April 10, 2019 9:25 PM, Chia-I Wu wrote:
> > Both implementations support formats that have no explicit modifiers.
> > But when it comes to buffer creation, modifier_hi/lo is required
> > again. It is unclear how to create a
On Wednesday, April 10, 2019 9:25 PM, Chia-I Wu wrote:
> Both implementations support formats that have no explicit modifiers.
> But when it comes to buffer creation, modifier_hi/lo is required
> again. It is unclear how to create a buffer for such formats.
>
> This patch tries to clarify these
In the prior version, "modifier" events could be used to advertise either
formats or modifiers. For example, they could be used to advertise formats
that have no modifiers, by setting the modifier_hi/lo to
DRM_FORMAT_MOD_INVALID.
In this version, "format" events are used to advertise formats and
On Mon, 8 Apr 2019 18:18:40 +0100
Daniel Stone wrote:
> Hi Drew,
> Thanks for writing this up! I think the broad concept is fine, but a
> few things jump out at me:
Hi,
thank you Drew indeed, you have clearly put a lot of thought in this.
It looks largely fine to me as well, and I pretty much
On Mon, 8 Apr 2019 23:14:32 +1200
Scott Anderson wrote:
> Do we want anything formal regarding the removal of protocols?
>
> The one comes to mind currently is xdg-shell-unstable-v5, which most (if
> not all?) compositors have dropped support for.
>
> If something previously widespread falls
On Tue, 9 Apr 2019 15:22:13 -0700
Chia-I Wu wrote:
> Format events are used to return supported formats while modifier
> evetns are used to return supported modifiers for each supported
> format.
>
> For example, if an implementation is based on EGL, it may send one
> format event for each
