aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorChris Wilson <[email protected]>2010-07-09 08:45:04 +0100
committerEric Anholt <[email protected]>2010-08-01 19:58:28 -0700
commitcda4b7d3a5b1dcbc0d8e7bad52134347798e9047 (patch)
tree100b176cd81d7cdf16c546b19ece124ab6a2588e /tools/perf/util/scripting-engines/trace-event-python.c
parent86f100b136626e91f4f66f3776303475e2e58998 (diff)
drm/i915: Unset cursor if out-of-bounds upon mode change (v4)
The docs warn that to position the cursor such that no part of it is visible on the pipe is an undefined operation. Avoid such circumstances upon changing the mode, or at any other time, by unsetting the cursor if it moves out of bounds. "For normal high resolution display modes, the cursor must have at least a single pixel positioned over the active screen.” (p143, p148 of the hardware registers docs). Fixes: Bug 24748 - [965G] Graphics crashes when resolution is changed with KMS enabled https://bugs.freedesktop.org/show_bug.cgi?id=24748 v2: Only update the cursor registers if they change. v3: Fix the unsigned comparision of x,y against width,height. v4: Always set CUR.BASE or else the cursor may become corrupt. Signed-off-by: Chris Wilson <[email protected]> Reported-by: Christian Eggers <[email protected]> Cc: Christopher James Halse Rogers <[email protected]> Cc: [email protected] Signed-off-by: Eric Anholt <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions