From: Max Krasnyansky <maxk@qualcomm.com>
To: Alexandros Karypidis <karypid@inf.uth.gr>,
bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hci_conn_info struct
Date: Thu, 09 Oct 2003 10:48:39 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20031009104727.059fba78@unixmail.qualcomm.com> (raw)
In-Reply-To: <200310092019.16955.karypid@inf.uth.gr>
At 10:19 AM 10/9/2003, Alexandros Karypidis wrote:
>Hi all,
>
>I am using hci_conn_info to obtain a list of devices I am connected to. I
>"stole" the code from looking at what "hcitool con" does. What I want to do
>now is figure out what the CoD of the peer device is. I would like to do that
>in a smart way.
>
>I tried doing an inquiry for devices, but I never receive the device I am
>connected to in the returned list of devices! Is this a limitation of
>Bluetooth or coincidence?
>
>In any case, it seems a little silly to scan for devices in order to find out
>the CoD of a device I am already connected to. Is there a way to achive this?
Actually if you don't specify IREQ_CACHE_FLUSH flag to hci_inquiry() it will
return cached results and device you're connected too will be on the list for sure.
Max
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-10-09 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 17:19 [Bluez-devel] hci_conn_info struct Alexandros Karypidis
2003-10-09 17:48 ` Max Krasnyansky [this message]
2003-10-09 18:09 ` Alexandros Karypidis
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=5.1.0.14.2.20031009104727.059fba78@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=karypid@inf.uth.gr \
/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