Frank Henigman writes:
> On Wed, Jun 12, 2013 at 1:33 PM, Eric Anholt wrote:
>> glCopyTexSubImage was just an example of "reads from texture and writes
>> to texture, thanks to FBOs" -- you've also got the normal drawing path,
>> glCopyPixels, glDrawPixels, glBitmap, glBlitFramebuffer. If zero-
On 06/12/2013 04:08 PM, Dave Airlie wrote:
On Thu, Jun 13, 2013 at 3:33 AM, Eric Anholt wrote:
Frank Henigman writes:
On Tue, Jun 11, 2013 at 1:10 PM, Eric Anholt wrote:
Frank Henigman writes:
Replace the one texture lock with a lock per texture. This allows
uploading textures from on
On Thu, Jun 13, 2013 at 3:33 AM, Eric Anholt wrote:
> Frank Henigman writes:
>
>> On Tue, Jun 11, 2013 at 1:10 PM, Eric Anholt wrote:
>>
>>> Frank Henigman writes:
>>>
>>> > Replace the one texture lock with a lock per texture. This allows
>>> > uploading textures from one thread concurrently
Frank Henigman writes:
> On Tue, Jun 11, 2013 at 1:10 PM, Eric Anholt wrote:
>
>> Frank Henigman writes:
>>
>> > Replace the one texture lock with a lock per texture. This allows
>> > uploading textures from one thread concurrently with drawing in another
>> > thread. _mesa_lock_context_textu
Frank Henigman writes:
> Replace the one texture lock with a lock per texture. This allows
> uploading textures from one thread concurrently with drawing in another
> thread. _mesa_lock_context_textures() was used to check for texture
> updates from other contexts and also to acquire the textur
On 06/10/2013 02:35 PM, Frank Henigman wrote:
Replace the one texture lock with a lock per texture. This allows
uploading textures from one thread concurrently with drawing in another
thread. _mesa_lock_context_textures() was used to check for texture
updates from other contexts and also to acq
