On Tue, Jan 8, 2013 at 10:32 AM, Chris Wilson <ch...@chris-wilson.co.uk> wrote: > On Tue, 8 Jan 2013 09:33:57 +0100, Daniel Vetter <daniel.vet...@ffwll.ch> > wrote: >> This could very well be caused by dirt left behind by the BIOS, so >> tune it down to the debug level. > > If the issue is solely the one described, then it should be silence when > we takeover, just like all the other error/debug status registers.
Good point, I'll check whether pimping gt_reset is good enough. > DRM_DEBUG is a little too noisy for this, maybe we should look at > trace_print or one of the other dynamic debugs for this class of info? The downside of trace_printk is that it doesn't pop up in dmesg. If all that reg checking starts to hurt, we might want to exclude the GT range from it - iirc this seemed most useful for display enabling. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
