From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error connecting after inquiry
Date: Thu, 19 Apr 2007 01:49:15 +0200 [thread overview]
Message-ID: <1176940155.6741.44.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1d49725d0704140901v7f778dd5tbe1b4fdfaef44430@mail.gmail.com>
Hi Donnie,
> Ok, the name is now only checked for devices that pass the class
> filter.
> Is there any way to ensure the baseband connection is closed?
I might have to fix that inside the kernel. A remote name complete event
should trigger a re-iteration of pending connect requests. This is not
simple. However you can call a remote name cancel command before
actually connecting to the device.
However the best for you is to use a high timeout for the name request
function. This will ensure that you catch the remote name complete
events and not abort before that. Use the values we use in hcitool,
because they are this long for a reason.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-18 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 16:01 [Bluez-devel] Error connecting after inquiry Donnie Smith
2007-04-18 23:49 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 19:42 Donnie Smith
2007-04-12 20:13 ` Marcel Holtmann
2007-04-12 3:05 Donnie Smith
2007-04-12 7:46 ` 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=1176940155.6741.44.camel@aeonflux.holtmann.net \
--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