On Mon, Dec 5, 2016 at 4:31 PM, Daniel Vetter wrote:
> On Mon, Dec 05, 2016 at 11:24:44AM +, Robert Bragg wrote:
> > Forgot to send to dri-devel when I first sent this out...
> >
> > The few times I've looked at using DRM_DEBUG messages, I haven't found
> > them very helpful considering how n
On Mon, Dec 05, 2016 at 11:24:44AM +, Robert Bragg wrote:
> Forgot to send to dri-devel when I first sent this out...
>
> The few times I've looked at using DRM_DEBUG messages, I haven't found
> them very helpful considering how noisy some of the categories are. More
> than once now I've prefe
Forgot to send to dri-devel when I first sent this out...
The few times I've looked at using DRM_DEBUG messages, I haven't found
them very helpful considering how noisy some of the categories are. More
than once now I've preferred to go in and modify individual files to
affect what messages I see
On Thu, Dec 01, 2016 at 05:18:00PM +, Robert Bragg wrote:
> I'm currently considering the use of DRM_ERROR in i915 perf for steam
> config validation errors (i.e. userspace misconfigurations) that should
> be changed so that i-g-t tests aren't treated as failures when
> triggering these.
>
> I
I'm currently considering the use of DRM_ERROR in i915 perf for steam
config validation errors (i.e. userspace misconfigurations) that should
be changed so that i-g-t tests aren't treated as failures when
triggering these.
I initially proposed changing these to DRM_INFO messages and
intentionally