From: Bastien Nocera <hadess@hadess.net>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-input@vger.kernel.org, linux-bluetooth@vger.kernel.org,
cbe-oss-dev@lists.ozlabs.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 2/2] hid/hid-sony: get and set Sixaxis bdaddr via sysfs
Date: Wed, 01 Sep 2010 18:41:46 +0100 [thread overview]
Message-ID: <1283362906.2361.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20100901192854.9370c605.ospite@studenti.unina.it>
On Wed, 2010-09-01 at 19:28 +0200, Antonio Ospite wrote:
> On Wed, 01 Sep 2010 17:17:54 +0100
> Bastien Nocera <hadess@hadess.net> wrote:
>
> > On Mon, 2010-05-03 at 22:15 +0200, Antonio Ospite wrote:
> > > Expose to userspace a simple way to get device bdaddr, and get/set master
> > > bdaddr on Sixaxis controller.
> > >
> > > Right now userspace softwares which manage pairing the controller with a
> > > bluetooth adapter, rely on libusb and hence have to detach and reattach
> > > usbhid, which is not very nice.
> > >
> > > Signed-off-by: Antonio Ospite <ospite@studenti.unina.it>
> > > ---
> > >
> > > As said, ideally this should be done with an interface such as hidraw, but its
> > > limitations prevent us from doing it the right way; and I am not going to
> > > touch hidraw myself anytime soon.
> >
> > Rest looks alright to me. Thanks!
>
> Bastien, Jiri, this patch can be DISCARDED. The hidraw work from Alan
> Ott (waiting for Marcel to ACK the bluetooth part) will make this kernel
> approach overkill.
>
> I already have some bluez patches based on Alan's work, but I am waiting
> for the needed changes to land into linus tree before submitting them.
>
> Sorry for making you wasting some time reviewing this one, I told you on
> IRC it could be discarded, but we know: "IRCs volant, emails manent".
Given the time it took me to review it, it's my own damn fault anyway ;)
next prev parent reply other threads:[~2010-09-01 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:15 [PATCH 0/2] Groundwork for Sixaxis paring into bluez Antonio Ospite
2010-05-03 20:15 ` [PATCH 1/2] hid/hid-sony: Apply sixaxis quirks only to sixaxis Antonio Ospite
[not found] ` <1272917756-31098-2-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-09-01 16:13 ` Bastien Nocera
[not found] ` <1283357615.2361.20.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-09-01 17:20 ` Antonio Ospite
2010-09-02 7:41 ` Jiri Kosina
2010-09-03 18:01 ` Antonio Ospite
2010-05-12 13:12 ` [PATCH 0/2] Groundwork for Sixaxis paring into bluez Antonio Ospite
[not found] ` <1272917756-31098-1-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-05-03 20:15 ` [PATCH 2/2] hid/hid-sony: get and set Sixaxis bdaddr via sysfs Antonio Ospite
[not found] ` <1272917756-31098-3-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-09-01 16:17 ` Bastien Nocera
2010-09-01 17:28 ` Antonio Ospite
2010-09-01 17:41 ` Bastien Nocera [this message]
2010-05-20 9:05 ` [PATCH 0/2] Groundwork for Sixaxis paring into bluez Antonio Ospite
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=1283362906.2361.25.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=ospite@studenti.unina.it \
/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).