Date: Wed, 4 Jan 2006 22:04:17 +0000 (GMT) From: wpaul@FreeBSD.ORG (Bill Paul) To: dalius.dobravolskas@gmail.com (Dalius Dobravolskas) Cc: psionic@csh.rit.edu, freebsd-current@freebsd.org Subject: Re: usb mouse support update plans Message-ID: <20060104220417.C903616A420@hub.freebsd.org> In-Reply-To: <98dd087e0601041155y4ee8a125v@mail.gmail.com> from Dalius Dobravolskas at "Jan 4, 2006 09:55:51 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello,
>
> > I think you can do this with usbhidaction(1).
> I would do it but I have not succeeded to make UHID device to work at all.
>
> > Once again, we need to know what usbdevs -v and usbhidctl have to say
> > before we can speculate further.
> I hope this list allows attachments. I think it is quite interesting
> to look at my results. I have tested system with ums in kernel and
> without it. If first case I have ums0 and uhid0 in second two uhid
> devices. The second uhid device (or the first when ums is in kernel)
> is not working for me. usbhidctl prints no valuable information. I
> have installed usbutil to my system as well. It printed some valuable
> information. uhid1 is both Keyboard (for page up and page down
> buttons) and Consumer device (for volume control buttons).
>
> I have checked /usr/share/misc/usb_hid_usages and found that following
> three lines corresponds to Volume Up, Volume Down and Mute:
> Usage(234)
> Usage(233)
> Usage(226)
>
> Best regards,
> Dalius
Looking at the output you sent me from usbctl, it appears there is
in fact one device with two interfaces. Interface 0 is the mouse and
interface 1 is the keyboard. It looks like the uhid0 device is supposed
to be the instance related to the keyboard (interface 1) but it's
not seeing the HID descriptors. I'm not sure why this is. Possibly
the code that's setting up the uhid device instance isn't setting the
iface number correctly. If the interface setting was correct, you
should have gotten more information from usbhidctl on uhid1.
Unfortunatelt, I can't really debug this without physical access to
the device, and even then I'm not sure I can help since I'm not all that
familiar with the guts of the USB code. (You can try building with
USB_DEBUG and turning on some of the verbose logging to see where it
might be going wrong.)
-Bill
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060104220417.C903616A420>