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. 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? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
