[PATCH] dmabuf: get supported dmabuf formats from compositor backend

[Daniel Stone]

Hi,

On 30 October 2015 at 00:27, Bryce Harrington <bryce at osg.samsung.com> wrote:
> On Tue, Oct 20, 2015 at 08:45:50AM -0700, Bryce Harrington wrote:
>> On Tue, Oct 20, 2015 at 04:54:30PM +0200, Fabien Dessenne wrote:
>> > Add the possibility for the compositor backend to provide with the list
>> > of supported pixel formats for dmabuf-based buffers.
>> > This information is used by linux_dmabuf to inform clients when binding.
>> >
>> > Signed-off-by: Fabien Dessenne <fabien.dessenne at st.com>
>>
>> Reviewed-by <bryce at osg.samsung.com>
>>
>> There's not a way to verify the list is getting sent across to the
>> client is there?
>
> Also, patch no longer applies since e3c0d8af.
>
> I'd like to better understand what this is going to be used for, before
> landing it.  Another R-b on this would be nice as well; Giulio perhaps
> you could give this patch a review?

Hm, to be honest I'd prefer this not land just now, or like this.

dmabuf usage in compositor-drm is just an optimisation, where the
fallback path is through gl-renderer. Anything gl-renderer doesn't
support, we essentially can't display. Those formats are what we need
to send to the compositor (possibly with the intersection between
gl-renderer and compositor-drm marked as preferred), but right now, as
the comment notes, we lack a way to query this through EGL. This is
being worked on though.

Cheers,
Daniel