public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: New property for DeviceFound signals to distinguish EIR devices
Date: Mon, 01 Dec 2008 18:05:44 +0100	[thread overview]
Message-ID: <1228151144.31158.151.camel@violet.holtmann.net> (raw)
In-Reply-To: <20081201164559.GA30372@localhost>

Hi Johan,

> > so I do like the idea of a boolean property. That is pretty simple. So
> > my current proposal would be "LegacyPairing". Since the Simple Pairing
> > should become the default and handles all the use cases right, we only
> > need to detect the cases for the old 2.0 and before devices.
> > 
> > However this has a limitation. We make the assumption that we always get
> > the Extended Inquiry Result. So setting LegacyPairing=True doesn't mean
> > that we are not doing Simple Pairing. It just means that we don't know
> > at this point of time if the remote device supports its. In practice we
> > might not be seeing this, but it is not mandatory for 2.1 devices to
> > enable Extended Inquiry Response.
> 
> I'd be fine with adding a LecacyPairing boolean both to the DeviceFound
> signal and the Device interface. I don't think the false-positive case
> is too bad since it shouldn't happen often and the UI can simply fall
> back to SSP then (which is a potential source of confusion for the user
> but at least the pairing can proceed).

okay. Then lets add a boolean "LegacyPairing" property and see how far
this helps us with improving the wizard.

Regards

Marcel



      reply	other threads:[~2008-12-01 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 15:53 New property for DeviceFound signals to distinguish EIR devices Johan Hedberg
2008-12-01 16:12 ` Marcel Holtmann
2008-12-01 16:45   ` Johan Hedberg
2008-12-01 17:05     ` 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=1228151144.31158.151.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=johan.hedberg@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox