On Wed, Jan 20, 2016 at 3:40 PM, Ian Romanick wrote:
> On 01/20/2016 12:34 PM, Matt Turner wrote:
>> On Wed, Jan 20, 2016 at 11:32 AM, Rob Clark wrote:
>>> From: Rob Clark
>>>
>>> The extension spec[1] describes DEBUG_TYPE_MARKER as "Annotation of the
>>> command stream". So for DEBUG_TYPE_MARK
On 01/20/2016 12:34 PM, Matt Turner wrote:
> On Wed, Jan 20, 2016 at 11:32 AM, Rob Clark wrote:
>> From: Rob Clark
>>
>> The extension spec[1] describes DEBUG_TYPE_MARKER as "Annotation of the
>> command stream". So for DEBUG_TYPE_MARKER, also pass the buf to the
>> driver's EmitStringMarker() t
On Wed, Jan 20, 2016 at 11:32 AM, Rob Clark wrote:
> From: Rob Clark
>
> The extension spec[1] describes DEBUG_TYPE_MARKER as "Annotation of the
> command stream". So for DEBUG_TYPE_MARKER, also pass the buf to the
> driver's EmitStringMarker() to be inserted in the command stream.
>
> [1] https
Reviewed-by: Ilia Mirkin
On Wed, Jan 20, 2016 at 2:32 PM, Rob Clark wrote:
> From: Rob Clark
>
> The extension spec[1] describes DEBUG_TYPE_MARKER as "Annotation of the
> command stream". So for DEBUG_TYPE_MARKER, also pass the buf to the
> driver's EmitStringMarker() to be inserted in the com
From: Rob Clark
The extension spec[1] describes DEBUG_TYPE_MARKER as "Annotation of the
command stream". So for DEBUG_TYPE_MARKER, also pass the buf to the
driver's EmitStringMarker() to be inserted in the command stream.
[1] https://www.opengl.org/registry/specs/KHR/debug.txt
Signed-off-by: R