linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>
Subject: [PATCH BlueZ] Add missing "Legacy" property for LE devices
Date: Thu, 12 Jan 2012 14:59:41 -0400	[thread overview]
Message-ID: <1326394781-465-1-git-send-email-anderson.lizardo@openbossa.org> (raw)

Some UIs may assume that a device lacking the Legacy property is
pre 2.1. To be more consistent with BR/EDR devices, always set Legacy
property explicitly to False. This makes these UIs not ask for a PIN
code when doing Just Works pairing for LE devices.
---
 src/adapter.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/adapter.c b/src/adapter.c
index e65780e..7e4bbb6 100644
--- a/src/adapter.c
+++ b/src/adapter.c
@@ -2671,11 +2671,14 @@ void adapter_emit_device_found(struct btd_adapter *adapter,
 		else
 			broadcaster = TRUE;
 
+		dev->legacy = FALSE;
+
 		emit_device_found(adapter->path, paddr,
 				"Address", DBUS_TYPE_STRING, &paddr,
 				"RSSI", DBUS_TYPE_INT16, &rssi,
 				"Name", DBUS_TYPE_STRING, &dev->name,
 				"Alias", DBUS_TYPE_STRING, &alias,
+				"LegacyPairing", DBUS_TYPE_BOOLEAN, &dev->legacy,
 				"Paired", DBUS_TYPE_BOOLEAN, &paired,
 				"Broadcaster", DBUS_TYPE_BOOLEAN, &broadcaster,
 				"UUIDs", DBUS_TYPE_ARRAY, &dev->uuids, uuid_count,
-- 
1.7.5.4


             reply	other threads:[~2012-01-12 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 18:59 Anderson Lizardo [this message]
2012-01-12 19:41 ` [PATCH BlueZ] Add missing "Legacy" property for LE devices Johan Hedberg

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=1326394781-465-1-git-send-email-anderson.lizardo@openbossa.org \
    --to=anderson.lizardo@openbossa.org \
    --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;
as well as URLs for NNTP newsgroup(s).