Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'ums'

This is an experimental report containing PRs for tag 'ums' as of 5-30-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 Thanks.

PRs for tag 'ums':
o2014/04/02kern/188186[drm] [ums] Intel DRM fails & USB KVM Mouse fails to function
o2014/02/01usb/186317usb[ums] ums module not loaded by devd for Razer Lachesis mouse
o2012/10/21usb/172931usb[ums] [suspend/resume] Suspend/resume blocks USB mouse
o2012/08/03usb/170358usb[ums] Wrong (duplicate) button numbers
o2010/01/02usb/142229usb[ums] [usb8] [hang] connecting a USB mouse to a Dell PE750 locks up kernel
o2009/11/24kern/140849usb[ums] [usb8] USB mouse doesn't work under FreeBSD 8.0-RELEASE
o2009/07/25usb/137129usb[ums] [usb8] SteelSeries Ikari USB laser mouse not attaching
p2008/11/10usb/128760cperciva[ums] [patch] patch for Microsoft Comfort Optical Mouse 3000 (model 1043)
o2008/07/15usb/125631usb[ums] [panic] kernel panic during bootup while 'Logitech USB receiver' (Logitech RX650 wireless mouse) is connected
o2008/01/25usb/119977usb[ums] Mouse does not work in a Cherry-USB keyboard/mouse-combo
o2007/11/09usb/117938usb[ums] [patch] Adding support for MS WL Natural and MS WL Optical (1008) mice
o2007/11/08usb/117911usb[ums] [request] Mouse Gembird MUSWC not work
s2006/09/24kern/103578[ums] ums does not recognize mouse buttons
s2006/04/20usb/96120usb[ums] [request] USB mouse not always detected
o2006/02/05usb/92852usb[ums] [patch] Vertical scroll not working properly on A4Tech WOP-49 optical mouse
o2005/07/19usb/83756usb[ums] [patch] Microsoft Intellimouse Explorer 4.0A doesn't work.
o2003/08/31kern/56250[ums] [patch] ums(4) doesn't work with MCT based PS/2 converters
17 problems total.

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.