Date: Wed, 23 Mar 2005 21:49:55 +0100 From: Marius =?ISO-8859-1?Q?N=FCnnerich?= <marius.nuennerich@gmx.net> To: freebsd-stable@freebsd.org Subject: Re: USB Mouse not working Message-ID: <20050323214955.6fdc2bcf@olaf.hackerzberg.dyndns.org> In-Reply-To: <200503220146.aa36398@salmon.maths.tcd.ie> References: <20050321102334.44abcc37@olaf.hackerzberg.dyndns.org> <200503220146.aa36398@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, 22 Mar 2005 01:46:19 +0000 Ian Dowse <iedowse@maths.tcd.ie> wrote: > > I'm not sure I do either :-) On a mouse I tried here I got very > different information than that: > > Report descriptor: > Collection page=Generic_Desktop usage=Mouse > Collection page=Generic_Desktop usage=Pointer > Input size=1 count=1 page=Button usage=Button_1, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_2, logical range 0..1 > Input size=1 count=1 page=Button usage=Button_3, logical range 0..1 > Input size=8 count=1 page=Generic_Desktop usage=X, logical range -127..127 > Input size=8 count=1 page=Generic_Desktop usage=Y, logical range -127..127 > Input size=8 count=1 page=Generic_Desktop usage=Wheel, logical range -127..127 > End collection > Feature size=1 count=1 page=Generic_Desktop usage=Motion_Wakeup, logical range 0..1 > End collection > Total input size 4 bytes > Total output size 0 bytes > Total feature size 0 bytes > > But I don't know enough about how this is supposed to work to make > sense of the difference. I got similar output, when I plug in that mouse with hw.usb.ums.debug=99: ums0: Device USB Device, rev 1.10/0.01, addr 2, iclass 3/1 ums_attach: bLength=7 bDescriptorType=5 bEndpointAddress=2-in bmAttributes=3 wMa xPacketSize=5 bInterval=10 ums0: 5 buttons and Z dir and a TILT dir. ums_attach: sc=0xc1a14000 ums_attach: X 8/8 ums_attach: Y 16/8 ums_attach: Z 24/8 ums_attach: B1 0/1 ums_attach: B2 1/1 ums_attach: B3 2/1 ums_attach: B4 3/1 ums_attach: B5 4/1 ums_attach: size=9, id=3 The TILT dir is caused by the hardcoded sc->flags |= UMS_T; Has anyone an idea what to do next? I suppose I can't do anything in ums.c, as it gets the (to few) data from another file. thanks Marius [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQdZ4Fqu2z7AvZZQRAgmHAKCCJzHu/FwENw+g3Til+rS4tsdJjQCgvzdL YYUAtVeNQoIzEGzsA7DRBt4= =2FOz -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050323214955.6fdc2bcf>