linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Szymon Janc <szymon.janc@codecoup.pl>
Cc: linux-bluetooth@vger.kernel.org, Juha Kuikka <juha.kuikka@gmail.com>
Subject: Re: [PATCH 8/9] plugins/sixaxis: Add support for DualShock 4/PS4 cable pairing
Date: Wed, 04 Oct 2017 14:40:56 +0200	[thread overview]
Message-ID: <1507120856.23708.18.camel@hadess.net> (raw)
In-Reply-To: <8659915.mKjsMy947m@ix>

On Wed, 2017-09-27 at 11:12 +0200, Szymon Janc wrote:
> Hi Bastien,
> 
> On Monday, 4 September 2017 20:12:11 CEST Bastien Nocera wrote:
> > From: Juha Kuikka <juha.kuikka@gmail.com>
> > 
> > This patch adds support for "pairing" a Dualshock4 controller over
> > USB
> > into the sixaxis plugin, similarly to what the Sixaxis/PS3
> > controller
> > supported.
> > 
> > Actual bonding happens on first connection, but the device will be
> > marked as trusted when the agent replies.
> > 
> > This patch is based on DS4 supprt for sixpair tool by t0xicCode:
> > https://github.com/t0xicCode/sixpair/commit/975c38cb6cd61a2f0be3507
> > 14f0f64ce
> > f5f0432c ---
> >  plugins/sixaxis.c | 73
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file
> > changed, 72
> > insertions(+), 1 deletion(-)
> > 
> > diff --git a/plugins/sixaxis.c b/plugins/sixaxis.c
> > index b62834d72..eb15acb92 100644
> > --- a/plugins/sixaxis.c
> > +++ b/plugins/sixaxis.c
> > @@ -83,10 +83,34 @@ static int sixaxis_get_device_bdaddr(int fd,
> > bdaddr_t
> > *bdaddr) return 0;
> >  }
> > 
> > +static int ds4_get_device_bdaddr(int fd, bdaddr_t *bdaddr)
> > +{
> > +	uint8_t buf[7];
> > +	int ret;
> > +
> > +	memset(buf, 0, sizeof(buf));
> > +
> > +	buf[0] = 0x81;
> > +
> > +	ret = ioctl(fd, HIDIOCGFEATURE(sizeof(buf)), buf);
> > +	if (ret < 0) {
> > +		error("ds4: failed to read device address (%s)",
> > +		      strerror(errno));
> 
> Lets prefix all sixaxis error/info logs with "sixaxis:"

Sure, I'll make some changes to mention whether the sixaxis or DS4
variant of the call was made.

Nothing else?

  reply	other threads:[~2017-10-04 12:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 18:12 [PATCH 1/9] plugins/sixaxis: Remove LEDs handling Bastien Nocera
2017-09-04 18:12 ` [PATCH 2/9] adapter: Add btd_request_authorization_cable_configured() Bastien Nocera
2017-09-04 18:12 ` [PATCH 3/9] sixaxis: Ask user whether cable configuration should be allowed Bastien Nocera
2017-09-27  9:12   ` Szymon Janc
2017-10-18  1:51     ` Bastien Nocera
2017-09-27  9:14   ` Szymon Janc
2017-10-04 12:38     ` Bastien Nocera
2017-09-04 18:12 ` [PATCH 4/9] plugins/sixaxis: Move device discovery to shared header Bastien Nocera
2017-09-05  9:03   ` Bastien Nocera
2017-09-05  9:13     ` Szymon Janc
2017-09-05 10:37       ` Bastien Nocera
2017-09-04 18:12 ` [PATCH 5/9] profiles/input: Use sixaxis header to simplify device detection Bastien Nocera
2017-09-04 18:12 ` [PATCH 6/9] profiles/input: Add DS4 devices to the shared header Bastien Nocera
2017-09-04 18:12 ` [PATCH 7/9] plugins/sixaxis: Rename sixaxis specific functions Bastien Nocera
2017-09-04 18:12 ` [PATCH 8/9] plugins/sixaxis: Add support for DualShock 4/PS4 cable pairing Bastien Nocera
2017-09-27  9:12   ` Szymon Janc
2017-10-04 12:40     ` Bastien Nocera [this message]
2017-10-18  1:51     ` Bastien Nocera
2017-09-04 18:12 ` [PATCH 9/9] plugins/sixaxis: Cancel cable pairing if unplugged Bastien Nocera
2017-09-27  9:07 ` [PATCH 1/9] plugins/sixaxis: Remove LEDs handling Szymon Janc

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=1507120856.23708.18.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=juha.kuikka@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@codecoup.pl \
    /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).