From: Bastien Nocera <hadess@hadess.net>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 3/4] Enable input/sixpair build (but no installation)
Date: Sat, 31 Dec 2011 00:47:27 +0100 [thread overview]
Message-ID: <1325288847.7327.2.camel@sirocco> (raw)
In-Reply-To: <20111230224753.6729859cbc78e1c68d8563af@studenti.unina.it>
Em Fri, 2011-12-30 às 22:47 +0100, Antonio Ospite escreveu:
> On Fri, 30 Dec 2011 15:26:10 -0400
> Anderson Lizardo <anderson.lizardo@openbossa.org> wrote:
>
> > "sixpair" is a standalone tool to manage PS3 controllers. It was the
> > only tool not being built by default.
> >
> > To build it, it is necessary to check for libusb-1.0 (besides the
> > existing libusb 0.1 check). The check is optional, and sixpair will not
> > be built if libusb-1.0 headers are not installed.
> > ---
> >
> > I personally never used this tool. So I'm not sure if the best approach is to
> > completely remove it instead. If that's the case, let me know so I send a patch
> > removing the .c file instead.
> >
>
> Hi Anderson,
>
> I'd say the .c file can be removed if you want to, when I have time I am
> going to resend the playstation-peripheral plugin and the prerequisite
> patches to have it as an _external_ plugin, I hope to do that next
> week.
>
> In my previous submissions of the playstation-peripheral plugin I was
> removing this .c file just before adding the new plugin, and I am going
> to "revert" this patch anyways, so you can choose to drop this patch
> and let me remove the .c file when I add the plugin, or remove it right
> now. I think there isn't much of a gain enabling the build of the
> sixpair.c currently in BlueZ.
>
> I am adding Bastien on CC as he was the author of the sixpair currently
> in BlueZ, Bastien what do you think?
Don't care. Been shipping a working-but-not-perfect version of a sixpair
plugin in the Fedora bluez package for at least 2 years. I'd be very
happy to drop that patch in favour of a supported version.
Cheers
next prev parent reply other threads:[~2011-12-30 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 19:26 [PATCH BlueZ 1/4] Remove PulseAudio plugin leftover Anderson Lizardo
2011-12-30 19:26 ` [PATCH BlueZ 2/4] Remove unused/broken "echo" RFCOMM plugin Anderson Lizardo
2011-12-30 19:26 ` [PATCH BlueZ 3/4] Enable input/sixpair build (but no installation) Anderson Lizardo
2011-12-30 21:47 ` Antonio Ospite
2011-12-30 23:47 ` Bastien Nocera [this message]
2011-12-31 12:22 ` Anderson Lizardo
2011-12-30 19:26 ` [PATCH BlueZ 4/4] Add missing options to bootstrap-configure Anderson Lizardo
2011-12-30 20:05 ` Marcel Holtmann
2012-01-09 12:53 ` [PATCH BlueZ 1/4] Remove PulseAudio plugin leftover Johan Hedberg
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=1325288847.7327.2.camel@sirocco \
--to=hadess@hadess.net \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@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