Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Feb 2009 20:51:10 +0100
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        freebsd-current@freebsd.org
Cc:        Giorgos Keramidas <keramida@ceid.upatras.gr>, Andrew Thompson <thompsa@freebsd.org>
Subject:   Re: usb2 moused issue (Microsoft Wireless Optical)
Message-ID:  <200902172051.11077.hselasky@c2i.net>
In-Reply-To: <200902172040.06348.hselasky@freebsd.org>
References:  <87mycme9wc.fsf@kobe.laptop> <87tz6sj2aw.fsf@kobe.laptop> <200902172040.06348.hselasky@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 17 February 2009, Hans Petter Selasky wrote:
> On Tuesday 17 February 2009, Giorgos Keramidas wrote:
> > On Tue, 17 Feb 2009 20:55:30 +0200, Giorgos Keramidas
> > <keramida@FreeBSD.org>
>
> wrote:
> > > The code of hid_report_size() is similar in old usb and the new usb
> > > stack, but I am not sure about all the differences I see.  The
> > > calculation of `size' is done correctly with old usb code, so I am
> > > testing the patch attached below now.  It essentially pulls in the
> > > hid_report_size() from the old usb code, with the if (h.kind == k)
> > > check reversed to remove one spurious indentation level:
> >
> > No luck with the old usb code for hid_report_size() either.  We may be
> > looking at the wrong place.  I'll build a kernel with a pre-usb2 stack
> > and see what ums debugging shows for this mouse.  If it used to work
> > with size=2 then we might have to look elsewhere for the bug.
>
> I don't think that will help. Can you try the following.
>
> XYZ information includes: (64+8-40)/8 = 4 bytes
>
> Then you need add one PD byte, so size should be 5 bytes.

Maybe this will help:

kldload usb2_quirk

And re-plug mouse? Because it looks like your mouse is already listed there.

BTW: I want to find a permanent solution for those quirks. So stand by for 
another patch.

--HPS



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