Re: siliconmotion CSync output ?

2007-03-12 Thread bruno schwander
I used your vclk setting code as in smi_driver.c, and changed the shift in SMI_CommonCalcClock() but it seems to still have some issue. 12220 clock gives me values of SR6C: 63, SR6D: 1D bruno On Sun, 11 Mar 2007, Alex Deucher wrote: On 3/10/07, bruno schwander [EMAIL PROTECTED] wrote: I

Re: siliconmotion CSync output ?

2007-03-12 Thread bruno schwander
On Mon, 12 Mar 2007, Alex Deucher wrote: On 3/12/07, bruno schwander [EMAIL PROTECTED] wrote: I used your vclk setting code as in smi_driver.c, and changed the shift in SMI_CommonCalcClock() but it seems to still have some issue. 12220 clock gives me values of SR6C: 63, SR6D: 1D That's

Re: siliconmotion CSync output ?

2007-03-10 Thread bruno schwander
are to be active, SR68 has to be configured too. bruno On Fri, 9 Mar 2007, Alex Deucher wrote: On 3/9/07, bruno schwander [EMAIL PROTECTED] wrote: On Fri, 9 Mar 2007, Alex Deucher wrote: The latest version of the siliconmotion driver in xorg git head should have the lockup fix you need

Re: siliconmotion CSync output ?

2007-03-09 Thread bruno schwander
On Fri, 9 Mar 2007, Alex Deucher wrote: On 3/9/07, bruno schwander [EMAIL PROTECTED] wrote: so I gather now that actually I should leave the xf86SetCrtcForModes() alone, and just add setting the clock with CCR6C, CCR6D (and enabling it with CCR68). I'll see how that goes... exactly. Sorry

Re: siliconmotion CSync output ?

2007-03-09 Thread bruno schwander
On Fri, 9 Mar 2007, Alex Deucher wrote: The latest version of the siliconmotion driver in xorg git head should have the lockup fix you need. The problem is the engine doesn't need to be synced until it has been started. I've also added dualhead support. I haven't yet pushed the pll fix,

Re: siliconmotion CSync output ?

2007-03-09 Thread bruno schwander
: On 3/9/07, bruno schwander [EMAIL PROTECTED] wrote: On Fri, 9 Mar 2007, Alex Deucher wrote: The latest version of the siliconmotion driver in xorg git head should have the lockup fix you need. The problem is the engine doesn't need to be synced until it has been started. I've also added

Re: siliconmotion CSync output ?

2007-03-08 Thread bruno schwander
On Thu, 8 Mar 2007, Tim Roberts wrote: bruno schwander wrote: ah never mind. since this is interlaced, the pixel clock needs to be half that to get the right frame refresh rate (60Hz) with a pixel clock of 12.22MHz, it passes. Now, I am not sure if the pixel clock is effectively set

Re: siliconmotion CSync output ?

2007-03-08 Thread bruno schwander
that programs vclk explicitely ? How can it set the crtc for several modes ? That is what xf86SetCrtcForModes() seems to do, right ? I still have a lot to learn. thanks for all the help guys, trudging along... bruno Alex Bruno On Wed, 7 Mar 2007, bruno schwander wrote: ah actually

Re: siliconmotion CSync output ?

2007-03-08 Thread bruno schwander
with CCR6C, CCR6D (and enabling it with CCR68). I'll see how that goes... bruno On Thu, 8 Mar 2007, bruno schwander wrote: On Thu, 8 Mar 2007, Alex Deucher wrote: The siliconmotion driver doesn't explicitly set the vclk pll. It uses the bios (if UseBIOS is set or does nothing

incomplete docs ?

2006-03-02 Thread bruno schwander
Hi all, I noticed some manpages and documentation is missing from the release information available at http://xfree86.org/current/RELNOTES4.html . Are these web pages automagically generated from the xfree86 sources ? bruno ___ Devel mailing list

Re: Live Touchscreen Calibration [WAS: magictouch touch screen driver]

2005-06-09 Thread bruno schwander
It would be great if you could add that... what do you mean by live calibration ? It seems to me that calibration should be (mostly) a userland utility, that you do not want to run everytime the Xserver starts. I probably misunderstood what you meant. My only issue currently, is that if

Re: magictouch touch screen driver

2005-06-03 Thread bruno schwander
On Thu, 26 May 2005, Andrew C Aitchison wrote: On Wed, 25 May 2005, bruno schwander wrote: I tried using the screenInfo everytime the x,y position is scaled and returned, but that does not seem to help. I do not know how to support screen resolition changes. If anybody has an idea, let me

Re: magictouch touch screen driver

2005-05-25 Thread bruno schwander
to clean. Here it is as a shell archive (don't know it the maillist rejects attachments...) bruno On Tue, 24 May 2005, David Dawes wrote: On Tue, May 24, 2005 at 08:05:43AM -0700, bruno schwander wrote: I have my driver for the serial MagicTouch touchscreen working. There is just one thing

Re: magictouch touch screen driver

2005-05-24 Thread bruno schwander
I have my driver for the serial MagicTouch touchscreen working. There is just one thing that I am not sure of: if the resolution is changed dynamically (by some program running fullscreen for example), the scaling is off. How do I find if the resolution has changed ? Right now, I check the screen