On Sat, Apr 22, 2017 at 11:53 PM, Mauro Rossi wrote:
> Hi Tomasz,
>
> last minute doubt
>
> 2017-04-19 9:00 GMT+02:00 Tomasz Figa :
>>
>> Android buffer queues can be abandoned, which results in failing to
>> dequeue next buffer. Currently this would
Hi Tomasz,
last minute doubt
2017-04-19 9:00 GMT+02:00 Tomasz Figa :
> Android buffer queues can be abandoned, which results in failing to
> dequeue next buffer. Currently this would fail somewhere deep within
> the DRI stack calling loader's getBuffers*(), without any error
On Fri, Apr 21, 2017 at 4:35 PM, Mauro Rossi wrote:
>
>
> 2017-04-20 18:51 GMT+02:00 Mauro Rossi :
>>
>>
>>
>> 2017-04-20 4:18 GMT+02:00 Tomasz Figa :
>>> I'd also like to hear from Mauro if this version, combined with the
>>>
2017-04-20 18:51 GMT+02:00 Mauro Rossi :
>
>
> 2017-04-20 4:18 GMT+02:00 Tomasz Figa :
>
>> On Wed, Apr 19, 2017 at 11:51 PM, Emil Velikov
>> wrote:
>> > Hi Tomasz,
>> >
>> > On 19 April 2017 at 08:00, Tomasz Figa
On 04/20/2017 07:51 PM, Mauro Rossi wrote:
2017-04-20 4:18 GMT+02:00 Tomasz Figa >:
On Wed, Apr 19, 2017 at 11:51 PM, Emil Velikov
> wrote:
> Hi Tomasz,
>
> On
2017-04-20 4:18 GMT+02:00 Tomasz Figa :
> On Wed, Apr 19, 2017 at 11:51 PM, Emil Velikov
> wrote:
> > Hi Tomasz,
> >
> > On 19 April 2017 at 08:00, Tomasz Figa wrote:
> >> Android buffer queues can be abandoned, which results in
On 04/19/2017 10:00 AM, Tomasz Figa wrote:
Android buffer queues can be abandoned, which results in failing to
dequeue next buffer. Currently this would fail somewhere deep within
the DRI stack calling loader's getBuffers*(), without any error
reporting to the client app. However Android
On Wed, Apr 19, 2017 at 11:51 PM, Emil Velikov wrote:
> Hi Tomasz,
>
> On 19 April 2017 at 08:00, Tomasz Figa wrote:
>> Android buffer queues can be abandoned, which results in failing to
>> dequeue next buffer. Currently this would fail somewhere
Hi Tomasz,
On 19 April 2017 at 08:00, Tomasz Figa wrote:
> Android buffer queues can be abandoned, which results in failing to
> dequeue next buffer. Currently this would fail somewhere deep within
> the DRI stack calling loader's getBuffers*(), without any error
> reporting
Android buffer queues can be abandoned, which results in failing to
dequeue next buffer. Currently this would fail somewhere deep within
the DRI stack calling loader's getBuffers*(), without any error
reporting to the client app. However Android framework code relies on
proper signaling of this
10 matches
Mail list logo