On 12/02/15 22:12, Ilia Mirkin wrote:
On Thu, Feb 12, 2015 at 3:09 PM, Martin Peres wrote:
On 12/02/15 04:05, Laura Ekstrand wrote:
This includes a v2 of all of the buffer object code plus a v2 of the
related
TextureBufferRange entry point.
Note that some implementations have been merged toge
Yes, Ilia's right. The _mesa_buffer_data backend is exposed to the rest of
the driver (for use in the near future in Meta), so it has "_meta". In
this v2, I discovered that some of the software fallbacks in bufferobj.c
were static and named "_mesa" (not my doing). I changed them in the v2 to
rem
On Thu, Feb 12, 2015 at 3:09 PM, Martin Peres wrote:
> On 12/02/15 04:05, Laura Ekstrand wrote:
>>
>> This includes a v2 of all of the buffer object code plus a v2 of the
>> related
>> TextureBufferRange entry point.
>>
>> Note that some implementations have been merged together (MapBuffer and
>>
On 12/02/15 04:05, Laura Ekstrand wrote:
This includes a v2 of all of the buffer object code plus a v2 of the related
TextureBufferRange entry point.
Note that some implementations have been merged together (MapBuffer and
MapBufferRange, for instance) because it didn't seem to make sense to keep
This includes a v2 of all of the buffer object code plus a v2 of the related
TextureBufferRange entry point.
Note that some implementations have been merged together (MapBuffer and
MapBufferRange, for instance) because it didn't seem to make sense to keep two
separate and nearly identical versions
