Bug#503029: problem recognized
On Fri, Dec 26, 2008 at 12:57:25AM +0100, Moritz Muehlenhoff wrote: forwarded 503029 http://bugzilla.kernel.org/show_bug.cgi?id=12297 thanks On Fri, Dec 26, 2008 at 12:33:59AM +0100, Radek Warowny wrote: There have been no related changes to the analog joystick driver up to 2.6.28. Could you report this at http://bugzilla.kernel.org and send the bug number to this bug? I have registered the bug at the http://bugzilla.kernel.org, the bug number is 10739. ITYM #12297, marking as forwarded. Unfortunately there was no reaction from the kernel developers. Does the bug still persist with a current kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110729145106.GA21347@pisco.westfalen.local
Bug#503029: problem recognized
forwarded 503029 http://bugzilla.kernel.org/show_bug.cgi?id=12297 thanks On Fri, Dec 26, 2008 at 12:33:59AM +0100, Radek Warowny wrote: There have been no related changes to the analog joystick driver up to 2.6.28. Could you report this at http://bugzilla.kernel.org and send the bug number to this bug? I have registered the bug at the http://bugzilla.kernel.org, the bug number is 10739. ITYM #12297, marking as forwarded. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503029: problem recognized
On Sat, Oct 25, 2008 at 03:29:38PM +0200, Radek Warowny wrote: I have recognized the problem I think. The issue occurs when you have cpu frequency scaling function activated. It appears when CPU was set to different frequency while inserting analog driver and different while reading joystick data (for example running a game). I think the problem is located in analog kernel driver and is related to usage of rdtscl() function to read time (in GET_TIME macro). This function returns number of clock ticks, not real time. So when cpu frequency changes the same difference (delta) of two reads is not the same difference of time (one clock lasts different time period). When the analog driver is loaded it computes some timing data that is used further while reading joystick state. When CPU frequency change occures it compares that timing data values with new timing reads which are differently scaled. A workaround (until the issue will be fixed) is to unload analog driver, set you CPU do fixed frequency, load the driver again an run you game. There have been no related changes to the analog joystick driver up to 2.6.28. Could you report this at http://bugzilla.kernel.org and send the bug number to this bug? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503029: problem recognized
I have recognized the problem I think. The issue occurs when you have cpu frequency scaling function activated. It appears when CPU was set to different frequency while inserting analog driver and different while reading joystick data (for example running a game). I think the problem is located in analog kernel driver and is related to usage of rdtscl() function to read time (in GET_TIME macro). This function returns number of clock ticks, not real time. So when cpu frequency changes the same difference (delta) of two reads is not the same difference of time (one clock lasts different time period). When the analog driver is loaded it computes some timing data that is used further while reading joystick state. When CPU frequency change occures it compares that timing data values with new timing reads which are differently scaled. A workaround (until the issue will be fixed) is to unload analog driver, set you CPU do fixed frequency, load the driver again an run you game. Regards Radek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
