From: Max Krasnyansky <maxk@qualcomm.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>,
Stephen Crane <steve.crane@rococosoft.com>
Cc: Philip Blundell <pb@nexus.co.uk>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: Version 3 libs/utils
Date: Thu, 17 Jul 2003 17:19:01 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030717171104.091fb2c0@unixmail.qualcomm.com> (raw)
In-Reply-To: <1057163407.963.122.camel@pegasus>
At 09:29 AM 7/2/2003, Marcel Holtmann wrote:
>> Asynchronous interface to inquiry?
>
>Yes, of course. I forgot this point. A common inquiry interface can
>maybe also included into btmgr and forward inquiry event to the
>application. Any ideas how to implement this in a clean way?
Should be easy. And there is no need to go via btmgr.
HCI core can simply filter hci_inquiry command and drop it if inquiry is already
in progress. Applications will simply listen on raw socket and invoke callbacks
for each inquiry_info event.
Max
next prev parent reply other threads:[~2003-07-18 0:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 0:03 Version 3 libs/utils Max Krasnyansky
2003-07-02 1:01 ` [Bluez-devel] " Marcel Holtmann
2003-07-02 8:34 ` Stephen Crane
2003-07-02 16:29 ` [Bluez-devel] " Marcel Holtmann
2003-07-18 0:19 ` Max Krasnyansky [this message]
2003-07-18 0:10 ` Max Krasnyansky
2003-07-18 0:33 ` [Bluez-devel] " Marcel Holtmann
2003-07-22 0:32 ` Max Krasnyansky
2003-07-22 10:06 ` Marcel Holtmann
2003-07-18 0:00 ` Max Krasnyansky
2003-07-18 0:51 ` [Bluez-devel] " Marcel Holtmann
2003-07-22 0:44 ` Max Krasnyansky
2003-07-22 10:40 ` Marcel Holtmann
2003-07-22 20:05 ` Max Krasnyansky
2003-07-22 21:33 ` Marcel Holtmann
2003-07-23 16:27 ` Max Krasnyansky
-- strict thread matches above, loose matches on Subject: below --
2003-06-21 0:13 [Bluez-devel] patch for d-bus support in hcid Max Krasnyansky
2003-06-24 17:31 ` Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid) Max Krasnyansky
2003-06-25 12:15 ` Marcel Holtmann
2003-06-26 17:15 ` Version 3 libs/utils Max Krasnyansky
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.20030717171104.091fb2c0@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
--cc=pb@nexus.co.uk \
--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