Subject: Re: [Bluez-devel] non-blocking device discovery
From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <1073308932.26243.1058.camel@baroque.rococosoft.com>
References: <1073308932.26243.1058.camel@baroque.rococosoft.com>
Content-Type: text/plain
Message-Id: <1073310252.2511.9.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Mon, 05 Jan 2004 14:44:12 +0100

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