Hey Tilman,
Kalle is having miscellaneous problems with MGA driver 1.9.100. He's
looking at the source code in-depth in 2 items below. So I guess it's
better to talk to you directly.
If you want more context, the whole (old) bug report is available at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403556
Kalle Olavi Niemitalo wrote:
- The DoubleScan flag seems to be ignored on the VGA2 output.
I am not entirely sure it worked in the previous version either.
However, the same mode works correctly on the VGA1 output.
I looked in xserver-xorg-video-mga_1.4.4.dfsg.1.orig.tar.gz
and it seems to ignore the V_DBLSCAN flag on the second CRTC
too. Perhaps the hardware doesn't support that feature?
However, in xserver-xorg-video-mga-1.9.100.dfsg.1/mga_driver.c,
MGAPreInit does this:
clockRanges->interlaceAllowed = !pMga->SecondCrtc;
clockRanges->doubleScanAllowed = TRUE;
If doublescan were not possible on the second CRTC, presumably
this would check pMga->SecondCrtc on the second line too?
Looks correct to me but Tilman will now more :)
- I don't get a mouse cursor on the second monitor. At first I
thought it might be some presentation feature, activated when
the monitors are displaying the same picture otherwise.
However it also happens when they are configured side by side.
In both versions, MGAGUseHWCursor in mga_dacG.c does:
if( pMga->SecondCrtc == TRUE )
return FALSE;
In 1.4.4.dfsg.1, MGAPreInitMergedFB used to set pMga->SecondCrtc
= TRUE. This code has apparently been removed from
1.9.100.dfsg.1; pMga->SecondCrtc is now always FALSE.
I presume MGAGUseHWCursor should now be somehow hooked to
crtc_mode_set in mga_g_crtc2.c, so that it begins returning
FALSE when the second CRTC is turned on.
The same problem has been reported by another user recently, I posted it
today on https://bugs.freedesktop.org/show_bug.cgi?id=13802
Merry Christmas,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
