Date: Mon, 25 Feb 2008 10:39:17 -0800 From: "Duane H. Hesser" <duane.hesser@gmail.com> To: freebsd-usb@freebsd.org Subject: Re: usb/121052: Microsoft Notebook Optical Mouse 3000 (model 1049) doesn't work Message-ID: <200802251839.m1PIdHrQ002097@belinda.androcles.org> In-Reply-To: <20080225171400.GB56247@plan0.kaiwan.csbnet.se> References: <200802242330.m1ONU4H3074911@freefall.freebsd.org> <20080225022450.GA40942@plan0.kaiwan.csbnet.se> <20080225075647.854d071f.dhesser@accima.com> <20080225171400.GB56247@plan0.kaiwan.csbnet.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 Feb 2008 18:14:00 +0100
Kai Wang <kaiwang27@gmail.com> wrote:
>
> The format of these report is really nice ;-)
>
thanks
>
> To figure out what these other report IDs really does, we could probably
> sniff the USB traffic under Windows with the mouse driver installed.
>
That might be possible if the features are used by the MS driver (in fact,
if they actually do anything). I strongly suspect that the reports are
bogus. I have a
Microsoft Microsoft<AE> 2.4GHz Transceiver V2.0, class 0/0, rev 2.00/2.50, addr 3, iclass 3/1
(Microsoft 2.4 Ghz wireless notebook mouse)
which has an identical report descriptor. That mouse *does* have 5 buttons
and a tilt wheel, and *doesn't* report spuriously on ID 0x15. I have watched the
0x15 data go by while testing my driver, but find no clue to what it is for.
Another way to look at the other reports is to have the driver ask for them by
ID. An ioctl added to the driver could allow 'mouse-report' to request input
reports and then read them when they come back.
---------
Duane Hesser
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802251839.m1PIdHrQ002097>