Date: Sun, 13 Mar 2005 02:57:38 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: "Loren M. Lang" <lorenl@alzatex.com> Cc: freebsd-usb@freebsd.org Subject: Re: USB Mouse detected as a generic hid device. Message-ID: <20050313105738.GA19869@alzatex.com> In-Reply-To: <20050313064312.GA16791@alzatex.com> References: <20050313041923.GA16329@alzatex.com> <20050313064312.GA16791@alzatex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 12, 2005 at 10:43:12PM -0800, Loren M. Lang wrote: > On Sat, Mar 12, 2005 at 08:19:23PM -0800, Loren M. Lang wrote: > > I have a Wireless USB Keyboard/Mouse Combo from Compaq. The actual id > > string says G Tech China USB Wireless mouse and keyboard. The keyboard > > is detected and works fine minus all of the extra multimedia keys, but > > the mouse doesn't work at all. The mouse is captured by the uhid driver > > and not the ums driver. I'd like to fix this, if possible, and send a > > patch in. The first thing I think I should do is look at the raw hid > > descriptor table and see what's different about it. Under windows xp, > > no special drivers were needed so I'm expecting it to not be too > > difficult from a regular usb mouse. What tools are available for > > extracting the raw descriptor tables from the usb device including all > > of the standard descriptors? I'd like something that can easily report > > as much detail as usbview for linux does, plus descriptors specific for > > hid devices. >=20 > I couldn't find any already made tools for this, so I've been playing > around with c and libusbhid to examine the keyboard/mouse combo and I > think I've figured out the problem. This wireless combo appears as just > a simple device with one interface (I think) and the report for the > mouse and keyboard are combined together. Does freebsd support having > keyboard and mouse events in the same report? If not, could I do > something like catch all the events through uhid0 and inject them back > into the kernel from a user-space program? The mouse is probably pretty > simple due to moused, but I don't know how I'd inject the keyboard > events. I just discovered vkbd, originally made to assist with bluetooth keyboards, but designed independent of bluetooth might do the job of letting me inject keyboard events into the kernel. Though this is probably more complicated then it should be. The ums and ukbd drivers should probably be written to work together instead. >=20 > > --=20 > > I sense much NT in you. > > NT leads to Bluescreen. > > Bluescreen leads to downtime. > > Downtime leads to suffering. > > NT is the path to the darkside. > > Powerful Unix is. > >=20 > > Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc > > Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 > > =20 >=20 >=20 >=20 > --=20 > I sense much NT in you. > NT leads to Bluescreen. > Bluescreen leads to downtime. > Downtime leads to suffering. > NT is the path to the darkside. > Powerful Unix is. >=20 > Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc > Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 > =20 --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 =20 --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCNByibTXoRwEYo9IRAqkBAJ4p0vsRc8tCKZJEVp3/+31zuE+UvgCfZ9f3 23J+S5oGgMGNemzm9Fpe5+4= =vlMe -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050313105738.GA19869>