actually several people on the xfree86 ML have reported the mouse going
over to one screen and not coming back, so it may be a bug with the
dualhead code.  I haven't had time to look into it, and the last time I
ran independant heads, I don't recall having that problem.
Also, regarding your modes, they may require a lower dot clock than
radeon supports.  I don't recall what the minimum clock is off hand. 
there is a patch in xfree86 cvs that lets you force the clock lower,
but YMMV and it may damage your hardware.

Alex

--- Mike Mestnik <[EMAIL PROTECTED]> wrote:
> I would like two separate heads.  Not trying to use mergedfb or
> xinerama.  It may be that this
> problem exists in Xfree86, I.E. not just a DRI CVS thing.  Since I'm
> running DRI I just want to
> ask before I post to the Xfree lists.
> 
> I have a LeftOf setup I'm using RightOf for this Layout, this makes
> things backwards.  When use Xv
> from time to time it flakes ought and I can't realy tell if it's X,
> the app, or the file i'm
> trying to play.
> 
> --- Alex Deucher <[EMAIL PROTECTED]> wrote:
> > Are you using mergedfb or not?  It's unclear to me.  if you are
> using
> > mergedfb, what problems are you having exactly?  if you enable the
> > Xinerama extenstion, tht will disable the built in mergedfb
> xinerama
> > extension.  that might be part of the problem.  Also what problems
> are
> > you having with Xv?  leftOf and rightOf describe crtc2's relation
> to
> > crtc1.  what do you mean by "backwards?"  also for mergedfb to use
> > modes they have to be listed in the screen section of your config. 
> if
> > you are looking for two separate heads (ie, host:0.0 and host:0.1)
> you
> > can't use mergedfb.  mergedfb only provides a single logical
> screen.
> > 
> > Alex
> > 
> > --- Mike Mestnik <[EMAIL PROTECTED]> wrote:
> > > 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/
> 
> __________________________________
> Do you Yahoo!?
> Free Pop-Up Blocker - Get it now
> http://companion.yahoo.com/


__________________________________
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

Reply via email to