Linux bluetooth development
 help / color / mirror / Atom feed
From: Antonio Ospite <ospite@studenti.unina.it>
To: Alan Ott <alan@signal11.us>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Marcel Holtmann <marcel@holtmann.org>,
	"Gustavo F. Padovan" <padovan@profusion.mobi>,
	"David S. Miller" <davem@davemloft.net>,
	Michael Poole <mdpoole@troilus.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	netdev@vger.kernel.org, Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH v5 0/4] Adding HID Feature Report Support to hidraw
Date: Tue, 1 Feb 2011 12:47:30 +0100	[thread overview]
Message-ID: <20110201124730.ac1faf74.ospite@studenti.unina.it> (raw)
In-Reply-To: <1295337880-12452-1-git-send-email-alan@signal11.us>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Tue, 18 Jan 2011 03:04:36 -0500
Alan Ott <alan@signal11.us> wrote:

> This patch adds Feature Report support for USB and Bluetooth HID devices
> through hidraw.
> 
> The first two patches prepare the bluetooth side for the change.
> 	a. Make sure the hidp_session() thread is started before
> 	   device's probe() functions are called.
> 	b. Wait for ACK/NAK on sent reports, and return proper
> 	   error codes.
> The third patch is the hidraw core and USB changes.

In particular, this third patch is a prerequisite for the bluez
sixaxis-cable plugin, originally written by Bastien Nocera (added to
CC) which I plan to submit when these changes are merged in mainline
linux.

[...]

-- 
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?

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2011-02-01 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  8:04 [PATCH v5 0/4] Adding HID Feature Report Support to hidraw Alan Ott
2011-01-18  8:04 ` [PATCH v5 1/4] bt hidp: Move hid_add_device() call to after hidp_session() has started Alan Ott
2011-01-18  8:04 ` [PATCH v5 2/4] bt hidp: Wait for ACK on Sent Reports Alan Ott
2011-01-18  8:04 ` [PATCH v5 3/4] hid: Add Support for Setting and Getting Feature Reports from hidraw Alan Ott
2011-01-18  8:04 ` [PATCH v5 4/4] bt hidp: Add support for hidraw HIDIOCGFEATURE and HIDIOCSFEATURE Alan Ott
2011-01-19 12:17 ` [PATCH v5 0/4] Adding HID Feature Report Support to hidraw Jiri Kosina
2011-02-10 18:14   ` Gustavo F. Padovan
2011-02-11 14:02     ` Jiri Kosina
2011-02-01 11:47 ` Antonio Ospite [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=20110201124730.ac1faf74.ospite@studenti.unina.it \
    --to=ospite@studenti.unina.it \
    --cc=alan@signal11.us \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hadess@hadess.net \
    --cc=jkosina@suse.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --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=netdev@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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