From: Antonio Ospite <ospite@studenti.unina.it>
To: Alan Ott <alan@signal11.us>
Cc: Jiri Kosina <jkosina@suse.cz>,
Alexey Dobriyan <adobriyan@gmail.com>, Tejun Heo <tj@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@suse.de>,
Stephane Chatty <chatty@enac.fr>,
Michael Poole <mdpoole@troilus.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] HID: Add Support for Setting and Getting Feature Reports from hidraw
Date: Thu, 10 Jun 2010 12:45:11 +0200 [thread overview]
Message-ID: <20100610124511.973a2ca5.ospite@studenti.unina.it> (raw)
In-Reply-To: <1276098868-3262-1-git-send-email-alan@signal11.us>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Wed, 9 Jun 2010 11:54:28 -0400
Alan Ott <alan@signal11.us> wrote:
> Per the HID Specification, Feature reports must be sent and received on
> the Configuration endpoint (EP 0) through the Set_Report/Get_Report
> interfaces. This patch adds two ioctls to hidraw to set and get feature
> reports to and from the device. Modifications were made to hidraw and
> usbhid.
>
> New hidraw ioctls:
> HIDIOCSFEATURE - Perform a Set_Report transfer of a Feature report.
> HIDIOCGFEATURE - Perform a Get_Report transfer of a Feature report.
>
> Signed-off-by: Alan Ott <alan@signal11.us>
Tested-by: Antonio Ospite <ospite@studenti.unina.it>
Regards,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-10 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 3:51 [PATCH] " Alan Ott
2010-06-08 6:32 ` Antonio Ospite
2010-06-08 13:42 ` Alan Ott
2010-06-09 8:42 ` Antonio Ospite
2010-06-09 15:20 ` Alan Ott
2010-06-09 15:54 ` [PATCH v2] " Alan Ott
2010-06-10 10:45 ` Antonio Ospite [this message]
2010-06-10 13:09 ` Jiri Kosina
2010-06-16 15:19 ` Jiri Kosina
2010-07-10 18:33 ` [PATCH v3 0/1] " Alan Ott
2010-07-10 18:33 ` [PATCH v3 1/1] " Alan Ott
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=20100610124511.973a2ca5.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=adobriyan@gmail.com \
--cc=alan@signal11.us \
--cc=chatty@enac.fr \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mdpoole@troilus.org \
--cc=stern@rowland.harvard.edu \
--cc=tj@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
all inboxes | Powered by JetHome®