From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: False negative checking for SSP support
Date: Sat, 13 Jun 2009 20:45:55 +0100 [thread overview]
Message-ID: <1244922355.11069.4410.camel@localhost.localdomain> (raw)
In-Reply-To: <1244921813.1852.2.camel@violet>
On Sat, 2009-06-13 at 21:36 +0200, Marcel Holtmann wrote:
> Hi Bastien,
>
> > 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?
> >
> > We already handle that case in the wizard, but it would be nicer if it
> > did detect it.
>
> it could be an older kernel or some other detail. Did you check with
> hciconfig hci0 sspmode that it is enabled on both sides? You can
> manually disable it (actually bluetoothd has to manually enable it).
SSP pairing works, between both machines, so I don't think that's the
problem (though the device creation never seems to finish).
> We might also have a bug in LegacyPairing property. Could be that it is
> not working correctly. Can you post dumps and further details.
It correctly detects a headset as being SSP. What kind of dumps do you
want? Just a dump on the computer that's initiating the pairing, from
the discovery process?
I'll update my bluez first on both machines, and test again.
Cheers
next prev parent reply other threads:[~2009-06-13 19:45 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 [this message]
2009-06-13 19:43 ` Johan Hedberg
2009-06-13 19:47 ` Marcel Holtmann
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=1244922355.11069.4410.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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.