linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] About bluetooth 2.1
Date: Wed, 31 Oct 2007 18:26:33 +0100	[thread overview]
Message-ID: <1193851593.32459.83.camel@violet> (raw)
In-Reply-To: <4728B6FD.50205@infitsrl.com>

Hi Fabrizio,

> I've read about optimized inquiry in bluetooth 2.1, If I understood 
> correctly the inquiry return remote device name and services list 
> information of the discovered remote devices.
> In current version to obtain the same result I've to make an inquiry a 
> name request and a sdp query for every remote device discovered.
> My question is, given that the new protocol is compatible with the old, 
> if I make an inquiry using a 2.1 dongle with blueZ I don't need to make 
> name and service  discovery or it's required because the optimized 
> inquiry works only between devices with 2.1 version?

you need to have Bluetooth 2.1 dongles and host stacks supporting 2.1 on
both sides to make this work.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-10-31 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 17:10 [Bluez-devel] About bluetooth 2.1 Fabrizio Guglielmino
2007-10-31 17:26 ` 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=1193851593.32459.83.camel@violet \
    --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;
as well as URLs for NNTP newsgroup(s).