On Jan 22, 2018 09:02, "Kenneth Graunke" wrote:
On Thursday, January 18, 2018 1:44:47 PM PST Chuck Atkins wrote:
> Is there a logging infrastructure currently available to drivers in Mesa?
> I was looking to clean up some of swr's debug / info output and have it
> conditional on the MESA_DEBUG an
On Jan 22, 2018 09:02, "Kenneth Graunke" wrote:
On Thursday, January 18, 2018 1:44:47 PM PST Chuck Atkins wrote:
> Is there a logging infrastructure currently available to drivers in Mesa?
> I was looking to clean up some of swr's debug / info output and have it
> conditional on the MESA_DEBUG an
On 01/18/2018 02:44 PM, Chuck Atkins wrote:
Is there a logging infrastructure currently available to drivers in
Mesa? I was looking to clean up some of swr's debug / info output and
have it conditional on the MESA_DEBUG and LIBGL_DEBUG variables but then
I realized that it's really something u
On Thursday, January 18, 2018 1:44:47 PM PST Chuck Atkins wrote:
> Is there a logging infrastructure currently available to drivers in Mesa?
> I was looking to clean up some of swr's debug / info output and have it
> conditional on the MESA_DEBUG and LIBGL_DEBUG variables but then I realized
> that
Hi;
On 01/18/2018 11:44 PM, Chuck Atkins wrote:
Is there a logging infrastructure currently available to drivers in
Mesa? I was looking to clean up some of swr's debug / info output and
have it conditional on the MESA_DEBUG and LIBGL_DEBUG variables but then
I realized that it's really someth
Is there a logging infrastructure currently available to drivers in Mesa?
I was looking to clean up some of swr's debug / info output and have it
conditional on the MESA_DEBUG and LIBGL_DEBUG variables but then I realized
that it's really something useful all across mesa so there may already be
som
