All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Anthony Bourguignon <contact@toniob.net>,
	linux-bluetooth@vger.kernel.org
Subject: Re: Can't connect a Xbox one controller
Date: Thu, 09 Nov 2017 14:49:17 +0100	[thread overview]
Message-ID: <1510235357.2624.9.camel@hadess.net> (raw)
In-Reply-To: <87inuqw9gs.fsf@intel.com>

On Wed, 2016-08-24 at 11:02 -0300, Vinicius Costa Gomes wrote:
> Hi,
> 
> Anthony Bourguignon <contact@toniob.net> writes:
> > > 
> > > No. It could be a bug in the xbox controller. But I need to take
> > > a
> > > closer look at the specification to be really sure.
> > 
> > Can I be of any help ?
> 
> Attached is a patch that disables negotiating Flow Control and
> Retransmission parameters for the SDP channel only. This is a shot in
> the dark, as I could find nothing in the specification that advises
> against the current BlueZ behaviour.
> 
> Could you give it a try? (but I don't have high hopes for it)
> 
> This is looking more like a bug in the controller.

Hi,

It's getting hit during pairing, but this isn't enough to get it
working.

I also combined it with vudentz' patch in the "Continuing the Xbox One
Bluetooth controller debugging" thread (called "Bluetooth: L2CAP:
Ignore Unknown option error for basic mode") and that wasn't enough to
get it working either.

I think that the fix would be to not try and upgrade the connection to
ERTM at all on this device, but I don't know how I could pass this
information down the stack to the l2cap code. Any ideas?

Cheers

  reply	other threads:[~2017-11-09 13:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 10:11 Can't connect a Xbox one controller Anthony Bourguignon
2016-08-18 13:56 ` Luiz Augusto von Dentz
2016-08-18 14:52   ` Anthony Bourguignon
2016-08-18 16:20     ` Luiz Augusto von Dentz
2016-08-18 17:46       ` Anthony Bourguignon
2016-08-19  8:43         ` Luiz Augusto von Dentz
2016-08-19  9:28           ` Anthony Bourguignon
2016-08-19 18:02 ` Vinicius Costa Gomes
     [not found]   ` <1471642506.3626.5.camel@toniob.net>
2016-08-19 23:34     ` Vinicius Costa Gomes
2016-08-20 12:54       ` Anthony Bourguignon
2016-08-24 14:02         ` Vinicius Costa Gomes
2017-11-09 13:49           ` Bastien Nocera [this message]
2017-11-09 14:28             ` Bastien Nocera
2017-11-09 15:11               ` Bastien Nocera
2017-11-13 10:04                 ` Bastien Nocera

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=1510235357.2624.9.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=contact@toniob.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.