[libhid-discuss] USB - HID query

[Anmol Ranka]

Hi,

Thanks for the reply. 

I have few more queries:

1) Within the HID interface I have few collections. In Windows, each
collection is treated as separate device.
I want to know that whether in Linux also, each collection is treated as
separate device or the all collections are treated as same device. 


2) How do I detach the device for kernel driver 'usbhid'. I tried modprobe -r
usbhid. But I got a error message
"FATAL: Module usbhid not found". 
Regards,
Anmol




-----Original Message-----
From: Charles Lepple [mailto:clepple at ghz.cc]
Sent: Mon 4/23/2007 4:42 PM
To: Anmol Ranka
Cc: libhid-discuss List
Subject: Re: [libhid-discuss] USB - HID query
 
On Apr 18, 2007, at 2:00 AM, Anmol Ranka wrote:

> It is compound device because, it consists of two different devices  
> embedded
> within a single device through a hub.

 From a programming standpoint, the "compound device" distinction is  
not important, because it should show up as two separate devices in  
the USB API.

> It is a composite device because within the same device, there are two
> functionalities i.e they same device belongs to audio as well as  
> HID class.

You can specify which interface to open.

> I downloaded the following package 'libhid_0.2.15 
> +20060325-2.1.tar.gz'. Is it
> OK to use this package for Fedora Core 5?

It hasn't been tested with Fedora specifically, but a few people have  
reported success.

> If yes, when I install this
> package, what will be the name of the libhid library that I have to  
> use and
> in which location would it be installed?

You can specify the location by passing --prefix= to ./configure. The  
library name is libhid.so.

> I also have following query:
>
> 1)To perform input and output operation, I need 'HID usage path'.  
> If I am
> right the HID Usage path is obtained from the HID Report  
> Descriptor. In order
> to know the HID report descriptor I executed the following command  
> provided
> by libhid:
>
> lsusb -d VID:PID -vvv.
>
> The partial output of this command is as follows.
>
> HID Device Descriptor:
>           bLength                 9
>           bDescriptorType        33
>           bcdHID               1.11
>           bCountryCode            0
>           bNumDescriptors         1
>           bDescriptorType        34 Report
>           wDescriptorLength     172
> cannot get report descriptor
>
> Why is the report descriptor not printed?

The kernel usbhid driver is probably still connected to that interface.

-- 
Charles Lepple






DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.