From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unexpected error / chronology trying to extract sdp handles
Date: Thu, 24 Jul 2008 16:18:33 +0200 [thread overview]
Message-ID: <1216909113.7820.16.camel@californication> (raw)
In-Reply-To: <488602EB.4000704@idlum.be>
Hi Pierre-Yves,
> > the SDP connection establishment might fail. This is different from from
> > any low-level ACL link that you see. Run hcidump -X -V and see what
> > actually does happen.
>
> Ok, so depending on when I get it, ConnectionAttempFailed might mean
> "ACL link establishment failed", or "SDP connection failed", or
> something else when triggered from elsewhere.
my guess in this case it means SDP connection failed since that is what
you requesting. It should not tell you about failures in other layers
since you don't care about them.
> And it is my duty to correctly figure out what it does mean at any given
> time. Is it right?
In this case run hcidump -X -V to actually figure out what happens. It
is always possible that we have a bug somewhere that nobody has
triggered before.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-07-24 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 11:13 [Bluez-devel] Unexpected error / chronology trying to extract sdp handles Pierre-Yves Paulus
2008-07-22 13:20 ` Marcel Holtmann
2008-07-22 15:55 ` Pierre-Yves Paulus
2008-07-24 14:18 ` Marcel Holtmann [this message]
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=1216909113.7820.16.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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