On Mon, 22 Apr, 2013 at 4:38 PM, christopher.halse.rog...@canonical.com
wrote:
From: Christopher James Halse Rogers
This is only exposed by drivers wich support the new PIPE_CAP_PRIME
parameter,
for PRIME import/export.
---
This stubs out texture_from_renderbuffer, which I don't care abou
On Mon, 2013-04-22 at 21:38 +1000, Dave Airlie wrote:
> On Mon, Apr 22, 2013 at 9:09 PM, Jose Fonseca wrote:
> > - Original Message -
> >> From: Christopher James Halse Rogers
> >>
> >> This is only exposed by drivers wich support the new PIPE_CAP_PRIME
> >> parameter,
> >> for PRIME impo
On Mon, Apr 22, 2013 at 9:09 PM, Jose Fonseca wrote:
> - Original Message -
>> From: Christopher James Halse Rogers
>>
>> This is only exposed by drivers wich support the new PIPE_CAP_PRIME
>> parameter,
>> for PRIME import/export.
>
> What does exactly PIPE_CAP_PRIME entail? Please docum
- Original Message -
> From: Christopher James Halse Rogers
>
> This is only exposed by drivers wich support the new PIPE_CAP_PRIME
> parameter,
> for PRIME import/export.
What does exactly PIPE_CAP_PRIME entail? Please document it.
Jose
___
m
From: Christopher James Halse Rogers
This is only exposed by drivers wich support the new PIPE_CAP_PRIME parameter,
for PRIME import/export.
---
This stubs out texture_from_renderbuffer, which I don't care about, but
that looks like it wouldn't be terribly painful to implement if it's a blocker
