public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Inquiry scans.
Date: Mon, 23 Feb 2004 18:21:26 +0100	[thread overview]
Message-ID: <1077556886.2791.51.camel@pegasus> (raw)
In-Reply-To: <403A1ECE.6030005@superbug.demon.co.uk>

Hi James,

> I have a Nokia 6310i mobile phone.
> It has a bluetooth menu item that says: -
> "Search for audio accessories"
> 
> If I activate this on the Nokia, it finds the Bluetooth headset.
> 
> In Bluez, in hcidump, I would expect to see these requests/responds 
> between those two devices, but I see nothing.

you will never see them, because this is the job of the link manager and
not the HCI layer.

> If bluez never sees the Inquiry scan from the Nokia, how will bluez ever 
> be able to respond?

You don't need this information on the host stack side. The Bluetooth
chip itself responds to it.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-02-23 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 15:39 [Bluez-devel] Inquiry scans James Courtier-Dutton
2004-02-23 17:04 ` Stephen Crane
2004-02-23 17:21 ` Marcel Holtmann [this message]
2004-02-23 17:38 ` Fred Schättgen

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=1077556886.2791.51.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=James@superbug.demon.co.uk \
    --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