Use of this function seems central for server-space use of DRI (as this
function sets up the DRIScreenPrivKey for use by dixLookupPrivate by way of
dixSetPrivate()). Yet this func is only called by I810DRIScreenInit() which is
only called by I810ScreenInit(); and this is only invoked only for va
Folks,
I understand that the normal method of debugging the GEM driver code is by
use of various debug functions conditionally included if/when various WATCH
manifests are defined.
So I set WATCH_COHERENCY for a port I am doing and that meant that
i915_gem_object_check_coherency() got called...bu