From: Marcel Holtmann <marcel@holtmann.org>
To: Nick Pelly <npelly@google.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fallback from eSCO to SCO on error code 0x1f (unspecified error).
Date: Tue, 24 Mar 2009 11:59:25 +0100 [thread overview]
Message-ID: <1237892365.4740.11.camel@localhost.localdomain> (raw)
In-Reply-To: <35c90d960903240922y2f956ccnd4f1c81092235fa@mail.gmail.com>
Hi Nick,
like I told everybody else; NO top posting.
> Here is the hcidump that prompted this patch:
>
> 009-03-23 17:43:50.727376 < HCI Command: Setup Synchronous Connection
> (0x01|0x0028) plen 17
> handle 1 voice setting 0x0060
> 2009-03-23 17:43:50.746969 > HCI Event: Command Status (0x0f) plen 4
> Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
> 2009-03-23 17:43:50.909963 > HCI Event: Synchronous Connect Complete
> (0x2c) plen 17
> status 0x1f handle 257 bdaddr 00:14:0A:01:E1:67 type eSCO
> Error: Unspecified Error
>
> I have confirmed that with this patch we successfully fall back to SCO
> with the Kyocera ED-8800
can you also send me the output of hcitool info, because this error is
kinda weird to get.
I am also suspicious about the TI chip now since I think that we are
working around the stupidity of that chip and not any kind of remote
headset. I would like to see the air trace (LMP negotiation) for this
specific headset.
Regards
Marcel
next prev parent reply other threads:[~2009-03-24 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 16:20 [PATCH] Bluetooth: Fallback from eSCO to SCO on error code 0x1f (unspecified error) Nick Pelly
2009-03-24 16:22 ` Nick Pelly
2009-03-24 10:59 ` Marcel Holtmann [this message]
2009-03-24 19:57 ` Nick Pelly
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=1237892365.4740.11.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=npelly@google.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