From: "Fred Schättgen" <bluez-devel@schaettgen.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] non-blocking device discovery
Date: Mon, 5 Jan 2004 20:12:34 +0100 [thread overview]
Message-ID: <200401052012.34307.bluez-devel@schaettgen.de> (raw)
In-Reply-To: <1073308932.26243.1058.camel@baroque.rococosoft.com>
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?
Maybe you were looking for this: http://cvs.sourceforge.net/viewcvs.py/
kde-bluetooth/kdebluetooth/libkbluetooth/? It's not part of the official KDE
distribution (yet), but it's in fact KDE/Qt code..
greetings
Fred
-------------------------------------------------------
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 19:12 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 [this message]
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=200401052012.34307.bluez-devel@schaettgen.de \
--to=bluez-devel@schaettgen.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.