Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
Agree this is orthogonal but just for the record
> >
> > I first
Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
>
> > I've made the updates locally, and see that it still builds
On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> From: Emil Velikov
...
>
> Takanari, Duncan,
> AFAICT the Renesas devices that you're using have an ImgTec IP inside
> them. Please check with Renesas and/or ImgTec, as one can build their
> driver as a Mesa component.
>
> As such you
Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
>
> > From checking header files it does seem to me that the layo
On 19 September 2017 at 06:24, Duncan Roe wrote:
> Hi Emil,
>
> On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
>> Hi Duncan,
>>
>> On 17 September 2017 at 09:04, Duncan Roe wrote:
>> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
>> >> From: Emil Velikov
> ...
>>
On 19 September 2017 at 05:34, Duncan Roe wrote:
> Hi Emil,
>
> On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
>> Hi Duncan,
>>
>> On 17 September 2017 at 09:04, Duncan Roe wrote:
>> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
>> >> From: Emil Velikov
> ...
>>
Hi Duncan,
On 17 September 2017 at 09:04, Duncan Roe wrote:
> On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
>> From: Emil Velikov
> ...
>>
>> Takanari, Duncan,
>> AFAICT the Renesas devices that you're using have an ImgTec IP inside
>> them. Please check with Renesas and/or ImgTe
On 15 September 2017 at 16:21, Daniel Stone wrote:
> Hi Emil,
>
> On 15 September 2017 at 15:54, Emil Velikov wrote:
>> On 15 September 2017 at 14:50, Daniel Stone wrote:
>>> Currently the client-facing libwayland-egl API is defined by a header
>>> file shipped by Wayland, but the implementation
Hi Emil,
On 15 September 2017 at 15:54, Emil Velikov wrote:
> On 15 September 2017 at 14:50, Daniel Stone wrote:
>> Currently the client-facing libwayland-egl API is defined by a header
>> file shipped by Wayland, but the implementation is left to each
>> vendor. This can cause collisions when m
Hi Dan,
Thanks for the quick review/feedback.
On 15 September 2017 at 14:50, Daniel Stone wrote:
> Hi Emil,
>
> On 15 September 2017 at 11:29, Emil Velikov wrote:
>> Currently we're in a bit of a pickle - both from vendor and user POV.
>
> This commit message is a bit long-winded. Could you ple
Hi Emil,
On 15 September 2017 at 11:29, Emil Velikov wrote:
> Currently we're in a bit of a pickle - both from vendor and user POV.
This commit message is a bit long-winded. Could you please try to
compress it down to something like:
Currently the client-facing libwayland-egl API is defined by
From: Emil Velikov
Currently we're in a bit of a pickle - both from vendor and user POV.
- User:
The wayland repository defines the wayland-egl interface.
At the same time, it leaves the actual implementation (DSO) and ways to
manage both files (wayland-egl.pc) to the vendor.
That is a bit con
12 matches
Mail list logo
