From: Zachary Lund <admin@computerquip.com>
To: linux-input@vger.kernel.org
Subject: Re: Xpad Driver Replacement
Date: Mon, 09 Dec 2013 21:27:31 -0600 [thread overview]
Message-ID: <52A68A23.7050707@computerquip.com> (raw)
In-Reply-To: <52A40F19.3020109@computerquip.com>
On 12/08/13 00:18, Zachary Lund wrote:
> Secondly, the Xbox 360 controllers claim to be HID compliant... this
> is not an HID driver. That's because the report descriptor is missing
> and I, unfortunately, do not know what to do about that. Some drivers
> like XBCD and the driver found at tattiebogle.net both provide their
> own report descriptor and work from there. While I'd like to do the
> same eventually, it will take me longer than a week to do that as I'd
> have to educate myself on HID and figure out what to do about the
> missing descriptors.
I've run into an instant road block. The controller claims
bInterfaceClass to be 0xFF (Vendor-specific) so usbhid won't probe it. I
didn't think it would be so difficult to work around that but I've spent
the better part of today trying to figure out just that. usbhid is a
usb_driver that has only one requirement to be probed: bInterfaceClass
be 0x03. Unfortunately, the device fails this requirement.
Does anyone know of a way around this mechanism? Or perhaps I should
take a different approach?
next prev parent reply other threads:[~2013-12-10 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 6:18 Xpad Driver Replacement Zachary Lund
2013-12-08 14:38 ` David Herrmann
2013-12-10 3:27 ` Zachary Lund [this message]
2013-12-14 5:16 ` Ken Phillis Jr
2013-12-19 9:24 ` David Herrmann
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=52A68A23.7050707@computerquip.com \
--to=admin@computerquip.com \
--cc=linux-input@vger.kernel.org \
/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).