Yes, you are right. I know that. The question is how to get it inside the xorg driver. Ajax's reply indicates that there is no existing way for me to get it inside xorg. Then, where should I go to fetch the data if not directly from something that I am "in control", the kernel driver?<br>
<br>I need a suggestion/solution. Thank you for your reply.<br><br>Ping<br><br><div class="gmail_quote">On Tue, Nov 3, 2009 at 10:13 AM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com">greg@kroah.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On Tue, Nov 03, 2009 at 10:03:18AM -0800, Ping wrote:<br>
> I need a quick answer since searching through the X server code takes too<br>
> long.<br>
><br>
> Is there a way for me to get the bInterfaceNumber from a device HID<br>
> Descriptor inside an xorg Input device driver? I feel there should be an<br>
> existing mechanism to fulfil this, maybe through an ioctl call? Can someone<br>
> show me what parameter(s) I need to use if the ioctl is supported?<br>
><br>
> Please also reply to me if you know there is no existing way to get the<br>
> bInterfaceNumber inside an xorg device driver so I will add my own<br>
> workaround in the kernel driver.<br>
<br>
</div></div>The kernel already exports this information to userspace, so you do not<br>
need to add it to your specific kernel driver. So it should be possible<br>
to do this for all USB devices.<br>
<br>
thanks,<br>
<br>
greg k-h<br>
</blockquote></div><br>