Hi,
First of all, thanks for the hard work!
Only one problem I noticed so far: when enabling virgl in drm_gralloc but
without support in MESA, MESA / drm_gralloc (?) will just crash during
initialization. I don't think it's that important but when I'm only using
i915 it shouldn't really need
On Fri, Mar 4, 2016 at 2:43 PM, Thomas Hellstrom wrote:
> On 03/04/2016 07:07 PM, Rob Clark wrote:
>> On Fri, Mar 4, 2016 at 12:59 PM, Rob Clark wrote:
>>> So, I've been advocating that for android, gallium drivers use
>>> gralloc_drm_pipe, since with android it seems like you end up with
>>> bot
On 03/04/2016 07:07 PM, Rob Clark wrote:
> On Fri, Mar 4, 2016 at 12:59 PM, Rob Clark wrote:
>> So, I've been advocating that for android, gallium drivers use
>> gralloc_drm_pipe, since with android it seems like you end up with
>> both gralloc and libGL in the same process, and having both share
On Fri, Mar 4, 2016 at 12:59 PM, Rob Clark wrote:
> So, I've been advocating that for android, gallium drivers use
> gralloc_drm_pipe, since with android it seems like you end up with
> both gralloc and libGL in the same process, and having both share the
> same pipe_screen avoids lots of headache
So, I've been advocating that for android, gallium drivers use
gralloc_drm_pipe, since with android it seems like you end up with
both gralloc and libGL in the same process, and having both share the
same pipe_screen avoids lots of headaches with multiple gem handles
pointing to same underlying buf
