All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: False negative checking for SSP support
Date: Sat, 13 Jun 2009 21:47:41 +0200	[thread overview]
Message-ID: <1244922461.1852.5.camel@violet> (raw)
In-Reply-To: <20090613194310.GA27600@jh-x301>

Hi Johan,

> > I'm slowly adding SSP 2.1 support to gnome-bluetooth. For that, I got a
> > laptop running Fedora 11, with a Bluetooth 2.1 dongle, in addition to
> > the one in the machine I'm trying to pair from.
> > 
> > Is there any reason why the other machine shows up as not supporting
> > SSP, when it actually does?
> 
> Do both of the machines support 2.1? The LegacyPairing property tells you
> whether SSP is likely to be triggered or not when you try to pair. It
> doesn't tell you whether other device supports SSP or not e.g. if your
> local adapter is pre-2.1 (but if your local adapter is 2.1 capable the
> property should be a good indicator of SSP support).
> 
> In theory it is possible to get a false positive for LegacyPairing if the
> other device is 2.1 but for some reason has extended inquiry response
> disabled (iirc the spec mandates EIR if SSP is enabled). However, if both
> sides have bluez and 2.1 HW then both EIR and SSP should automatically be
> get enabled by bluetoothd. If that's not happening we may have a bug
> somewhere (which I haven't seen with any of my 2.1 adapters).

it is actually the other way around. You can only use EIR if you enable
SSP. However you can have SSP without EIR.

Regards

Marcel



  reply	other threads:[~2009-06-13 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 19:06 False negative checking for SSP support Bastien Nocera
2009-06-13 19:36 ` Marcel Holtmann
2009-06-13 19:45   ` Bastien Nocera
2009-06-13 19:43 ` Johan Hedberg
2009-06-13 19:47   ` Marcel Holtmann [this message]
2009-06-13 23:21   ` Bastien Nocera

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=1244922461.1852.5.camel@violet \
    --to=marcel@holtmann.org \
    --cc=hadess@hadess.net \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.