PRs for tag 'psm'
This is an experimental report containing PRs for tag 'psm' as of 4-20-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'psm':
|o||2013/12/17||kern/184951||[psm] ps2 mouse detected but no psm0 device created|
|o||2012/12/14||kern/174441||[psm] [patch] Enable detection of Synaptics touchpad for firmware >= 7.5|
|a||2011/09/26||kern/161043||jhb||[psm] PS/2 mouse does not work in 9.0-BETA2/-CURRENT [regression]|
|o||2011/07/20||kern/159063||[psm] ALPS touchpad recognized as PS mouse (no scrl, nor r-click)|
|o||2009/09/18||kern/138938||[psm] Synaptics Support dosn't work on Dell Latitude d600|
|o||2009/07/28||kern/137228||[psm] synaptics support delays 'mouse up' events when no motion|
|o||2008/11/24||kern/129125||[psm] psm0: failed to reset the aux device.|
|f||2008/10/23||kern/128308||gavin||[psm] psm0 cause page fault|
|o||2008/10/14||kern/128083||[psm] [panic] early SMP panic on GA-G31M-S2L motherboard with PS/2 mouse|
|o||2008/03/24||kern/122046||[psm] Synaptics touchpad freezes (psm0: lost interrupt?) [regression]|
|o||2007/12/31||kern/119197||[psm]: PS/2 mouse doesn't work under FreeBSD i386 7.0|
|o||2007/02/14||kern/109161||philip||[psm] synaptic touchpad doesn't work|
|o||2007/02/01||kern/108659||[psm] Mouse (Synaptics touchpad) cursor freezes for some seconds (~5sec) in X|
|o||2006/07/21||kern/100687||[psm] psm problem (?): touchpad hangs, then move super slowly with no acceleration|
|o||2006/01/05||kern/91339||[psm] mousedriver do not recognize aditional buttons on psm|
|o||2000/04/29||kern/18293||[psm] [patch] lack of versapad mouse wheel emulation|
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.