From 85d118ee288fe7aa32db003bfa322ddf06944bf6 Mon Sep 17 00:00:00 2001 From: Paulo Cesar Pereira de Andrade Date: Fri, 14 Nov 2008 22:04:17 -0200 Subject: Don't explicitly call the cursor routines. On the MSOC, the hardware cursor was remaining on screen, when using EXA and a randr rotated mode. --- src/smi_crtc.c | 20 -------------------- 1 file changed, 20 deletions(-) (limited to 'src/smi_crtc.c') diff --git a/src/smi_crtc.c b/src/smi_crtc.c index d061ad5..329a907 100644 --- a/src/smi_crtc.c +++ b/src/smi_crtc.c @@ -82,9 +82,6 @@ SMI_CrtcPrepare(xf86CrtcPtr crtc) ENTER(); - if (pSmi->HwCursor) - crtc->funcs->hide_cursor(crtc); - LEAVE(); } @@ -96,23 +93,6 @@ SMI_CrtcCommit(xf86CrtcPtr crtc) ENTER(); - /* Problem: - * When starting in Dualhead mode, both hw cursors will be shown, - * and at the same position, as both are at the same address. - * When reconfiguring with something like: - * $ xrandr --output VGA --right-of LVDS - * what will happen is basically: - * hide_cursor(panel) - * hide_cursor(crt) - * - * show_cursor(panel) <- besides a sw argb cursor is being used... - * - * It should not be a problem if argb cursors were supported, - * or only one output is available... - */ - if (pSmi->HwCursor) - xf86_reload_cursors(pScrn->pScreen); - LEAVE(); } -- cgit v1.2.3