From: Greg KH <greg@kroah.com>
To: Matt Silva <msilva-dev@protonmail.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Supporting a USB HID device interface that is missing a interrupt input endpoint
Date: Fri, 27 May 2022 08:13:20 +0200 [thread overview]
Message-ID: <YpBsALSkBNNqp+HR@kroah.com> (raw)
In-Reply-To: <Ga58tkH_TZsMUGfo6cNG-kSqI3aYfH0GezcYcQyC4hr4GDd77vR_7Pc7tSnbI8C3gYnF7sZ60CWjOZQ3AAUxD0piYn0XrRkRmOjM3InxEMQ=@protonmail.com>
On Thu, May 26, 2022 at 08:06:46PM +0000, Matt Silva wrote:
> Hey, Greg.
>
> I went ahead and started implementing the changes in libusb as per your recommendation. But I'm following up cause you asked about the usbhid-dump output.
>
> > But this really is not a HID device, right?
>
> Well, Windows does decide to recognize it as a HID device. I captured some packets send to the device's control endpoint of unknown transfer type with URB function: URB Function: URB_FUNCTION_GET_MS_FEATURE_DESCRIPTOR (0x002a). Perhaps that has something to do with this as my research says that MS OS Descriptors indicate which driver Windows should use.
Ah, yeah, this info, and the hid descriptor dump you provided means this
is ment to be controlled from userspace with a vendor-specific program
like you are writing using libusb.
So you are on the right path, nice work!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-05-27 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 23:40 Supporting a USB HID device interface that is missing a interrupt input endpoint Matt Silva
2022-05-17 6:18 ` Greg KH
2022-05-18 22:04 ` Matt Silva
2022-05-19 7:38 ` Greg KH
2022-05-26 20:06 ` Matt Silva
2022-05-27 6:13 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YpBsALSkBNNqp+HR@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=msilva-dev@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).