From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] non-blocking device discovery
Date: Mon, 05 Jan 2004 14:44:12 +0100 [thread overview]
Message-ID: <1073310252.2511.9.camel@pegasus> (raw)
In-Reply-To: <1073308932.26243.1058.camel@baroque.rococosoft.com>
Hi Stephen,
> 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?
I posted examples of this on the mailing list some time ago. You can
also take a look at libs2/lib/bluetooth.c and see the bt_inquiry()
function. This function is not yet complete, but it should give you a
general idea how it works.
Regards
Marcel
-------------------------------------------------------
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-05 13:44 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 [this message]
2004-01-05 19:12 ` Fred Schättgen
2004-01-06 15:34 ` Stephen Crane
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=1073310252.2511.9.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=steve.crane@rococosoft.com \
/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