All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: "Fred Schättgen" <bluez-devel@schaettgen.de>,
	"BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] non-blocking device discovery
Date: Wed, 07 Jan 2004 05:44:13 +0100	[thread overview]
Message-ID: <1073450652.2508.116.camel@pegasus> (raw)
In-Reply-To: <1073403253.26243.1099.camel@baroque.rococosoft.com>

Hi Stephen,

> Now onto my new question, what are the semantics of OCF_INQUIRY? I seem
> to be getting one unique device per inquiry call. That is I get one
> EVT_INQUIRY_RESULT event with a bdaddr I haven't seen before and then it
> terminates with an EVT_INQUIRY_COMPLETE. For example:
> 
> inquiry
> found 00:aa:bb:cc:dd:ee
> inquiry complete
> ...
> inquiry
> found 00:aa:bb:cc:dd:ee
> found 00:aa:bb:cc:dd:ef
> inquiry complete
> 
> ...and so on. It seems that when it finds a new device, it passes that
> back up and exits inquiry mode. Can this be right (or have I fscked
> up)?  It only stays in inquiry mode for the specified length of time
> when there are no new devices to be found.

this is not the whole story. What you see is the behaviour of the CSR,
Ericsson and ST based devices, which filter out duplicates. The devices
from Nokia, Broadcom and AVM report every device and it is possible that
you see some bdaddr's more than once.

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

      parent reply	other threads:[~2004-01-07  4: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
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 [this message]

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=1073450652.2508.116.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez-devel@schaettgen.de \
    --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 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.