On 11/13/2013 12:52 AM, Maarten Lankhorst wrote:
> op 12-11-13 22:49, Thomas Hellstrom schreef:
>> On 11/12/2013 07:26 PM, Maarten Lankhorst wrote:
>>> Most drivers have refcounting done in gem, so lets get rid of another
>>> refcounting layer. ;)
>>> It has been confusing to keep track of 2 refco
op 12-11-13 22:49, Thomas Hellstrom schreef:
> On 11/12/2013 07:26 PM, Maarten Lankhorst wrote:
>> Most drivers have refcounting done in gem, so lets get rid of another
>> refcounting layer. ;)
>> It has been confusing to keep track of 2 refcounts, so lets just let the
>> driver worry about
>> re
On 11/12/2013 07:26 PM, Maarten Lankhorst wrote:
> Most drivers have refcounting done in gem, so lets get rid of another
> refcounting layer. ;)
> It has been confusing to keep track of 2 refcounts, so lets just let the
> driver worry about
> refcounting, and keep it hidden from ttm entirely. The
Most drivers have refcounting done in gem, so lets get rid of another
refcounting layer. ;)
It has been confusing to keep track of 2 refcounts, so lets just let the driver
worry about
refcounting, and keep it hidden from ttm entirely. The core doesn't need to
know about the
refcounting anywhere.
