public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Continuous Inquiry
Date: Sun, 02 Jan 2005 21:11:57 +0100	[thread overview]
Message-ID: <1104696717.8894.28.camel@pegasus> (raw)
In-Reply-To: <BAY12-F96C49A8056B58A97FFE7BAB9F0@phx.gbl>

Hi,

> I am a bit lost here.
> 
> I looked at the code for hic_inquiry and hci_send_req... still not sure how 
> to read raw socket event for inquiry.  Any other pointer to look at?

th point is using the HCI raw socket directly. Sending the HCI inquiry
command and then reading the inquiry results events. There is example
code for that in the mailing list archive.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-02 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-01  8:02 [Bluez-devel] Continuous Inquiry Pegasus ...
2005-01-01 18:48 ` Marcel Holtmann
2005-01-01 21:10   ` Pegasus ...
2005-01-01 23:36     ` Marcel Holtmann
2005-01-01 22:36       ` [Bluez-devel] Bluz APi Anderson Clayton
2005-01-02 10:58         ` Marcel Holtmann
2005-01-02 21:04           ` RES: " Anderson Clayton
2005-01-03  0:49             ` Marcel Holtmann
2005-01-02 19:37       ` [Bluez-devel] Continuous Inquiry Pegasus ...
2005-01-02 20:11         ` Marcel Holtmann [this message]
2005-01-04 13:06     ` Steven Singer

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=1104696717.8894.28.camel@pegasus \
    --to=marcel@holtmann.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox