From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "Johan Hedberg" <johan.hedberg@gmail.com>
Cc: "BlueZ development" <linux-bluetooth@vger.kernel.org>
Subject: Re: HBH-PV270 headset get locked
Date: Tue, 25 Nov 2008 11:34:35 -0300 [thread overview]
Message-ID: <2d5a2c100811250634vd53daafvce6791992a3c621@mail.gmail.com> (raw)
In-Reply-To: <C2133416-B233-4FFF-B29B-0BCF3B3402E1@gmail.com>
yep, client->dev = NULL seems to be a bug, although by looking the log
it seems there is another problem, the sco connection doesn't succeed
but it still attempt to send the file descriptor. The logic on a2dp is
a little different, since it doesn't start the stream on
BT_SETCONFIGURATION_REQ and unlock the sep in any possible error.
Btw, I couldn't reproduce the problem here by using aplay, arecord or
even both together.
--
Luiz Augusto von Dentz
Engenheiro de Computação
next prev parent reply other threads:[~2008-11-25 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 4:10 HBH-PV270 headset get locked Sam Lin
2008-11-25 8:14 ` Sam Lin
2008-11-25 9:15 ` Johan Hedberg
2008-11-25 14:34 ` Luiz Augusto von Dentz [this message]
2008-11-26 0:09 ` Sam Lin
2008-11-26 10:06 ` Sam Lin
2008-11-26 13:05 ` 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=2d5a2c100811250634vd53daafvce6791992a3c621@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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