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.

2 files changed, 0 insertions, 24 deletions

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)
-     *	<set-crt-mode-and-modify-mapped-address>
-     *	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();
 }
 
diff --git a/src/smi_driver.c b/src/smi_driver.c
index 8b6e78b..d8ba8ab 100644
--- a/src/smi_driver.c
+++ b/src/smi_driver.c
@@ -1017,10 +1017,6 @@ SMI_EnterVT(int scrnIndex, int flags)
     if (!xf86SetDesiredModes(pScrn))
 	RETURN(FALSE);
 
-    /* Initialize the hardware cursor */
-    if (pSmi->HwCursor)
-	xf86_show_cursors(pScrn);
-
     /* Reset the grapics engine */
     if (!pSmi->NoAccel)
 	SMI_EngineReset(pScrn);