On Fri, Sep 22, 2017 at 6:18 PM, Matt Hoosier wrote:
> On Fri, Sep 22, 2017 at 10:24 AM, Pekka Paalanen wrote:
>> On Wed, 20 Sep 2017 07:11:57 -0700
>> Daniel Stone wrote:
>>
>>> Hi Matt,
>>>
>>> On 20 September 2017 at 05:48, Matt Hoosier wrote:
>>> > On a related subject, there was discussion
On Fri, Sep 22, 2017 at 10:24 AM, Pekka Paalanen wrote:
> On Wed, 20 Sep 2017 07:11:57 -0700
> Daniel Stone wrote:
>
>> Hi Matt,
>>
>> On 20 September 2017 at 05:48, Matt Hoosier wrote:
>> > On a related subject, there was discussion back at
>> > https://lists.freedesktop.org/archives/wayland-de
On Wed, 20 Sep 2017 07:11:57 -0700
Daniel Stone wrote:
> Hi Matt,
>
> On 20 September 2017 at 05:48, Matt Hoosier wrote:
> > On a related subject, there was discussion back at
> > https://lists.freedesktop.org/archives/wayland-devel/2013-September/011091.html
> > that acknowledged a longstandin
Hi Emre,
On 20 September 2017 at 06:38, Ucan, Emre (ADITG/ESB)
wrote:
> Will this protocol be used by libEGL, or applications has to use it directly ?
The idea was for whoever calls wl_surface_attach() to also attach the
fence: an EGL/Vulkan driver, or a client framework directly if using
buffer
Hi Matt,
On 20 September 2017 at 05:48, Matt Hoosier wrote:
> On a related subject, there was discussion back at
> https://lists.freedesktop.org/archives/wayland-devel/2013-September/011091.html
> that acknowledged a longstanding bug where wl_buffer::release events
> are starved indefinitely in t
Behalf Of Daniel Stone
> Sent: Mittwoch, 20. September 2017 01:46
> To: wayland-devel@lists.freedesktop.org
> Subject: [PATCH wayland-protocols] Add
> zwp_linux_explicit_synchronization_v1
>
> Signed-off-by: Daniel Stone
> ---
> Makefile.am
On Tue, Sep 19, 2017 at 6:46 PM, Daniel Stone wrote:
> Signed-off-by: Daniel Stone
> ---
> Makefile.am| 1 +
> unstable/linux-explicit-synchronization/README | 5 +
> .../linux-explicit-synchronization-unstable-v1.xml | 208
> +
Signed-off-by: Daniel Stone
---
Makefile.am| 1 +
unstable/linux-explicit-synchronization/README | 5 +
.../linux-explicit-synchronization-unstable-v1.xml | 208 +
3 files changed, 214 insertions(+)
create mode 100644 unstable/l
