Hey,
Op 19-03-2019 om 00:27 schreef Ayan Halder:
> On Mon, Mar 18, 2019 at 07:12:24PM +0100, Maarten Lankhorst wrote:
>> Op 18-03-2019 om 16:40 schreef Brian Starkey:
>>> Hi,
>>>
>>> On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
>>>
>>>
>>>
Hey..
There's a
On Mon, Mar 18, 2019 at 07:12:24PM +0100, Maarten Lankhorst wrote:
> Op 18-03-2019 om 16:40 schreef Brian Starkey:
> > Hi,
> >
> > On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
> >
> >
> >
> >> Hey..
> >>
> >> There's a conflict with this patch and the merge of
On Mon, Mar 18, 2019 at 07:06:39PM +, Brian Starkey wrote:
> > [1]
> > https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/commit/0ac7d1187b234e86157ad74937c249a3c016807c
>
> Eh. I'm not familiar enough with the gitlab UI. Looks like this didn't
> merge in GStreamer so far.
Gah! Still
On Mon, Mar 18, 2019 at 07:00:57PM +, Brian Starkey wrote:
> On Mon, Mar 18, 2019 at 07:12:24PM +0100, Maarten Lankhorst wrote:
> > Op 18-03-2019 om 16:40 schreef Brian Starkey:
> > > Hi,
> > >
> > > On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
> > >
> > >
> > >
> > >>
On Mon, Mar 18, 2019 at 07:12:24PM +0100, Maarten Lankhorst wrote:
> Op 18-03-2019 om 16:40 schreef Brian Starkey:
> > Hi,
> >
> > On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
> >
> >
> >
> >> Hey..
> >>
> >> There's a conflict with this patch and the merge of
Op 18-03-2019 om 16:40 schreef Brian Starkey:
> Hi,
>
> On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
>
>
>
>> Hey..
>>
>> There's a conflict with this patch and the merge of topic/hdr-formats,
>> resulting in double definitions for Y210, Y410 and P010.
>>
>> Worse still is
Hi,
On Mon, Mar 18, 2019 at 11:17:55AM +0100, Maarten Lankhorst wrote:
> Hey..
>
> There's a conflict with this patch and the merge of topic/hdr-formats,
> resulting in double definitions for Y210, Y410 and P010.
>
> Worse still is that one has set has_alpha to true for Y41x and other to
Op 12-03-2019 om 19:16 schreef Ayan Halder:
> From: Brian Starkey
>
> As we look to enable AFBC using DRM format modifiers, we run into
> problems which we've historically handled via vendor-private details
> (i.e. gralloc, on Android).
>
> AFBC (as an encoding) is fully flexible, and for example
From: Brian Starkey
As we look to enable AFBC using DRM format modifiers, we run into
problems which we've historically handled via vendor-private details
(i.e. gralloc, on Android).
AFBC (as an encoding) is fully flexible, and for example YUV data can
be encoded into 1, 2 or 3 encoded
