|
Bugzilla – Full Text Bug Listing |
| Summary: | Mouse Polling Support | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Schneider <asn> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | chiranjeevi.am |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Schneider
2006-01-17 19:56:12 UTC
Hmm, I think SaX shouldn't modify the modprobe.conf ? and the on the fly setup said: ---snip-- There is, sort of. You can change the value the driver uses as the overriding-value, by writing to the file /sys/module/usbhid/parameters/mousepoll. However, to make use of this newly set value, you have to re-plug your mouse. Alternatively, you could also re-load the usbhid module with a new polling interval. This, of course, only works when usbhid is built as a module. It should also be noted, that things like X.org might not like to suddenly lose a driver while running. You have been warned. --snap--- this seems to be not very userfriendly as well, and yes X doesn't like to loose the input device ;) any opinion about this one ? set to remind mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( *** Bug 1143846 has been marked as a duplicate of this bug. *** |