linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: smcoe1 <smcoe1@gmail.com>
Cc: Nick Pelly <npelly@google.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] eSCO fallback to SCO on Error: Connection Failed to Complete
Date: Fri, 12 Feb 2010 18:56:42 +0100	[thread overview]
Message-ID: <1265997402.21559.0.camel@localhost.localdomain> (raw)
In-Reply-To: <9c9ad6a31002120806m381e6548xacf28c5ba9b079de@mail.gmail.com>

Hi Stephen,

> Thanks, I guess I wasn't really paying attention, it was a late nite.
> 
> Signed-off-by: Stephen Coe <smcoe1@gmail.com>
> ---
>   net/bluetooth/hci_event.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 592da5c..6c57fc7 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -1698,6 +1698,7 @@ static inline void
> hci_sync_conn_complete_evt(struct hci_dev *hdev, struct sk_bu
>  		hci_conn_add_sysfs(conn);
>  		break;
> 
> +	case 0x11:	/* Unsupported Feature or Parameter Value */
>  	case 0x1c:	/* SCO interval rejected */
>  	case 0x1a:	/* Unsupported Remote Feature */
>  	case 0x1f:	/* Unspecified error */

I need a proper patch with the hcidump and the name of the device that
causes this issue. See how Nick has done it lately.

Regards

Marcel



  reply	other threads:[~2010-02-12 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 20:56 [PATCH] eSCO fallback to SCO on Error: Connection Failed to Complete smcoe1
2010-02-11 21:20 ` Nick Pelly
2010-02-12 16:06   ` smcoe1
2010-02-12 17:56     ` Marcel Holtmann [this message]
2010-02-16 15:21       ` smcoe1
2010-02-16 15:40         ` Marcel Holtmann

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=1265997402.21559.0.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=npelly@google.com \
    --cc=smcoe1@gmail.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 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).