This is a MFB problem, I think.
I had just setup gamecon for my nintendo controlers and wanted a fullscreen
experiance. I'm told
I want "[EMAIL PROTECTED]" for the best view. I also want to be able to use my other
head for normal
things. I have a radeon8900. I hooked my Xconfig up with a good asortmant of modes I
might use,
from http://xtiming.sourceforge.net/cgi-bin/xtiming.pl.
Mostly I use 'startx -- +xinerama -layout XiLayout', I will use MFB when it becomes
stable. As it
is now I have problems with XV and I don't want to bounce back and forth trying to
debug them.
My setup is LeftOf, but for this odd layout I thought it would be ok to try RightOf.
AFAIKT This
worked, albeit backwards. My plan was to run sawfish only on one display and just
have the nes
emulator deal withought any wm.
When I tryied to run 'startx -- -layout TVideoLayout' I had 2 problems. The mouse
moved off my
primary head onto the secondary but then it was stuck there. The second is more of a
driver
problem than a MFB one. Most of the modes I had defined didn't take here is that
info, and my
question.
Modeline "[EMAIL PROTECTED]" 10.45 240 272 288 320 256 261 264 269 doublescan
Modeline "[EMAIL PROTECTED]" 9.58 256 288 304 336 224 228 231 236 doublescan
Modeline "[EMAIL PROTECTED]" 11.00 256 288 304 336 256 261 264 269 doublescan
Modeline "[EMAIL PROTECTED]" 10.21 320 352 368 400 200 204 206 211 doublescan
Modeline "[EMAIL PROTECTED]" 12.37 320 352 368 400 240 245 248 253 doublescan
Modeline "[EMAIL PROTECTED]" 18.96 400 432 464 496 300 306 309 316 doublescan
Modeline "[EMAIL PROTECTED]" 30.76 512 544 600 632 384 392 396 404 doublescan
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
(II) RADEON(0): Not using mode "[EMAIL PROTECTED]" (bad mode
clock/interlace/doublescan)
<SNIP>
(**) RADEON(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 87.1 Hz (D)
(II) RADEON(0): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace
doublescan
+hsync +vsync
"512x384" worked(it's a builtin mode), do I have to use interlace with doublescan?
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
