On Thu, Oct 1, 2015 at 10:30 AM, Emil Velikov wrote:
> Hi Rob,
>
> I believe that Marek managed to nicely explain how things work.
> Ideally you'll be able to get on the same boat (i.e. the Android C
> runtime/linker won't give you the finger). Regardless some comments
> inline.
>
> On 30 Septembe
On Thu, Oct 1, 2015 at 3:53 PM, Rob Clark wrote:
> On Wed, Sep 30, 2015 at 7:37 PM, Marek Olšák wrote:
>> On Wed, Sep 30, 2015 at 10:43 PM, Rob Clark wrote:
>>> From: Rob Clark
>>>
>>> Not actually working yet, ie. doesn't even compile yet, but an idea.
>>>
>>> Initial motivation was for drm_gr
Hi Rob,
I believe that Marek managed to nicely explain how things work.
Ideally you'll be able to get on the same boat (i.e. the Android C
runtime/linker won't give you the finger). Regardless some comments
inline.
On 30 September 2015 at 21:43, Rob Clark wrote:
> From: Rob Clark
>
> Not actual
On Wed, Sep 30, 2015 at 7:37 PM, Marek Olšák wrote:
> On Wed, Sep 30, 2015 at 10:43 PM, Rob Clark wrote:
>> From: Rob Clark
>>
>> Not actually working yet, ie. doesn't even compile yet, but an idea.
>>
>> Initial motivation was for drm_gralloc/pipe, which is essentially a sort
>> of mini state-t
On Wed, Sep 30, 2015 at 10:43 PM, Rob Clark wrote:
> From: Rob Clark
>
> Not actually working yet, ie. doesn't even compile yet, but an idea.
>
> Initial motivation was for drm_gralloc/pipe, which is essentially a sort
> of mini state-tracker, that needs to be able to share pipe_screen with
> lib
From: Rob Clark
Not actually working yet, ie. doesn't even compile yet, but an idea.
Initial motivation was for drm_gralloc/pipe, which is essentially a sort
of mini state-tracker, that needs to be able to share pipe_screen with
libGL linked into the same process (to ensure we didn't end up with
