From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem With the Inquiry and RFCOMM conexions
Date: Fri, 17 Mar 2006 13:56:00 +0100 [thread overview]
Message-ID: <1142600160.4392.22.camel@localhost> (raw)
In-Reply-To: <001001c644f0$2c3d9130$0300a8c0@akira>
Hi,
> I have a problem with make a Inquiry and RFCOMM conexions at the same
> time and don=C2=B4t understand why.....(with BlueZ).
> =20
> Is It possible in the same module of bluetooth make a inquiry
> (independ thread) and RFCOMM conexions (4 o 5 conexions in independ
> threads) =20
> at the same time?
> =20
> If I use diferent handles for this the call HCI to the module ...
> Is it independient?=20
you can use as many handles as you like, but the underlaying HCI device
is still the same. It doesn't allow inquiries while you are connecting
to another device. However newer chips allow to run an inquiry while you
are connected (still not while connecting).
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-17 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 9:31 [Bluez-devel] Problem With the Inquiry and RFCOMM conexions Sir Graham (Terra)
2006-03-17 12:56 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 9:52 Sir Graham (Terra)
2006-03-13 13:32 ` Marcel Holtmann
2006-03-13 14:15 ` Sir Graham (Terra)
2006-03-17 12:58 ` Marcel Holtmann
2006-03-15 9:08 Sir Graham (Terra)
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=1142600160.4392.22.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).