Date: Thu, 20 May 1999 19:23:49 +0200 (MET DST) From: Jean-Marc Zucconi <jmz@FreeBSD.ORG> To: dawes@rf900.physics.usyd.edu.au Cc: thyerm@camtech.com.au, current@FreeBSD.ORG Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) Message-ID: <199905201723.TAA04440@qix.jmz.org> In-Reply-To: <19990520224919.B4105@rf900.physics.usyd.edu.au> (message from David Dawes on Thu, 20 May 1999 22:49:19 %2B1000) References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> <19990519182237.H29455@rf900.physics.usyd.edu.au> <3742C5B7.5E85F408@camtech.com.au> <19990520224919.B4105@rf900.physics.usyd.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> David Dawes writes: > IMHO the problem is in the joystick driver and in your assumptions. By > configuring the joystick in your Xserver config file, you're giving the > server exclusive use of the device for the lifetime of the X server > process. Implementing more agressive closing might solve your particular > problem, but it doesn't deal with the real problem of the joystick driver > causing the silo overflows. All interrupts are blocked when you read the joystick position, and this is the reason of the silo overflows. It is almost impossible to avoid (it could be possible to use a very high frequency timer and to check the joystick status during the interrupts, but this has an impact on the precision of the position). However keeping the device opened can't cause silo overflows. It seems rather than the X server continues to read the joystick position after the client stops using it. This can be considered as a bug in the X server. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905201723.TAA04440>