Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2006 19:06:02 -0800
From:      "Eugene M. Kim" <blue@white.lv>
To:        usb@freebsd.org
Subject:   Request for testing, PR usb/106565: [PATCH] ums(4) does not work if the mouse defaults to boot protocol
Message-ID:  <457E1C9A.8060509@white.lv>

next in thread | raw e-mail | index | archive | help
Greetings,

If you have a mouse that exhibits some of the following symptoms, could 
you test the patch found within 
http://www.freebsd.org/cgi/query-pr.cgi?pr=106565 and provide feedback?

    * The mouse wheel does not work.

    * In some cases, when you move the mouse cursor and/or presses a
      button, the mouse behaves as if its wheel were turned (and
      consequently moves the scrollbar of the current window, for example).

    * Rarely, the mouse is recognized but does not work at all, except
      when you press a certain combination of buttons (usually the left
      button only) and the cursor moves erratically and spurious button
      events are generated (i.e. the mouse behaves as if some other
      buttons are pressed).

    * You cannot bring a window to the top by clicking in it; you have
      to click its window decoration (such as the title bar or a
      border).  At least this happened to me when using metacity, the
      default window manager of GNOME.


In a nutshell, the problem is that the mouse erroneously defaults not to 
the standard "report" protocol, but to the "boot" protocol (used by 
motherboards and embedded systems for "legacy emulation") when it is 
attached and configured.  This presumably happened because developers of 
the problematic model of mouse had a broken motherboard that did not 
specifically configure the mouse into the boot protocol, which they had 
to work around.

The patch solves the problem by forcing ums(4) to reset the mouse back 
into the report protocol so that it reports its full status that 
includes mouse wheels and more than three buttons.  This aligns to the 
USB 2.0 specification, which recommends resetting the protocol although 
the mouse should already default to the report protocol.

Cheers,
Eugene



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?457E1C9A.8060509>