From: Stephen Crane <steve.crane@rococosoft.com>
To: "Fred Schättgen" <bluez-devel@schaettgen.de>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] non-blocking device discovery
Date: 06 Jan 2004 15:34:14 +0000 [thread overview]
Message-ID: <1073403253.26243.1099.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <200401052012.34307.bluez-devel@schaettgen.de>
Hi Fred and list,
Yeah that was the code I was referring to. (It is also very similar to
the code I'd cobbled together from Marcel's libs2 and the old
hci_inquiry() from libs1.)
Now onto my new question, what are the semantics of OCF_INQUIRY? I seem
to be getting one unique device per inquiry call. That is I get one
EVT_INQUIRY_RESULT event with a bdaddr I haven't seen before and then it
terminates with an EVT_INQUIRY_COMPLETE. For example:
inquiry
found 00:aa:bb:cc:dd:ee
inquiry complete
...
inquiry
found 00:aa:bb:cc:dd:ee
found 00:aa:bb:cc:dd:ef
inquiry complete
...and so on. It seems that when it finds a new device, it passes that
back up and exits inquiry mode. Can this be right (or have I fscked
up)? It only stays in inquiry mode for the specified length of time
when there are no new devices to be found.
I have set the inquiry time parameter to 0x30 and the number of devices
to 0xff (both the max as per the spec).
TIA,
Steve
On Mon, 2004-01-05 at 19:12, Fred Sch=E4ttgen wrote:
> On Monday 05 January 2004 14:22, Stephen Crane wrote:
> > Hi,
> > I seem to remember a posting to this list in which someone mentioned
> > that they'd implemented non-blocking device-discovery by writing
> > commands directly to the hci socket. The code was C++ which leads me =
to
> > think that it was part of KDE but I can't find it on the net.
> >
> > Can someone refresh my memory?
>=20
> Maybe you were looking for this: http://cvs.sourceforge.net/viewcvs.py/
> kde-bluetooth/kdebluetooth/libkbluetooth/? It's not part of the officia=
l KDE=20
> distribution (yet), but it's in fact KDE/Qt code..
>=20
> greetings
> Fred
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM=
's
> Free Linux Tutorials. Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
--=20
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-06 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 13:22 [Bluez-devel] non-blocking device discovery Stephen Crane
2004-01-05 13:44 ` Marcel Holtmann
2004-01-05 19:12 ` Fred Schättgen
2004-01-06 15:34 ` Stephen Crane [this message]
2004-01-06 15:53 ` Stephen Crane
2004-01-07 4:44 ` 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=1073403253.26243.1099.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.de \
/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