From: Jerzy Kasenberg <jerzy.kasenberg@tieto.com>
To: <linux-bluetooth@vger.kernel.org>
Cc: Jerzy Kasenberg <jerzy.kasenberg@tieto.com>
Subject: [PATCH 7/8] android/client: Add pin handling for bind
Date: Fri, 8 Nov 2013 13:48:29 +0100 [thread overview]
Message-ID: <1383914910-2304-8-git-send-email-jerzy.kasenberg@tieto.com> (raw)
In-Reply-To: <1383914910-2304-1-git-send-email-jerzy.kasenberg@tieto.com>
This patch ask user for ping in pin_request_cb, which does
what otherwise would be required to manually type
bluetooth pin_reply address pin.
---
android/client/if-bt.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/android/client/if-bt.c b/android/client/if-bt.c
index 4c501a5..0a580e1 100644
--- a/android/client/if-bt.c
+++ b/android/client/if-bt.c
@@ -16,6 +16,7 @@
*/
#include "if-main.h"
+#include "terminal.h"
const bt_interface_t *if_bluetooth;
@@ -209,14 +210,33 @@ static void discovery_state_changed_cb(bt_discovery_state_t state)
static char last_remote_addr[MAX_ADDR_STR_LEN];
static bt_ssp_variant_t last_ssp_variant = (bt_ssp_variant_t) -1;
+static bt_bdaddr_t pin_request_addr;
+static void pin_request_answer(char *reply)
+{
+ bt_pin_code_t pin;
+ int accept = 0;
+ int pin_len = strlen(reply);
+
+ if (pin_len > 0) {
+ accept = 1;
+ if (pin_len > 16)
+ pin_len = 16;
+ memcpy(&pin.pin, reply, pin_len);
+ }
+
+ EXEC(if_bluetooth->pin_reply, &pin_request_addr, accept, pin_len, &pin);
+}
+
static void pin_request_cb(bt_bdaddr_t *remote_bd_addr, bt_bdname_t *bd_name,
uint32_t cod)
{
/* Store for command completion */
bt_bdaddr_t2str(remote_bd_addr, last_remote_addr);
+ pin_request_addr = *remote_bd_addr;
haltest_info("%s: remote_bd_addr=%s bd_name=%s cod=%06x\n", __func__,
last_remote_addr, bd_name->name, cod);
+ terminal_prompt_for("Enter pin: ", pin_request_answer);
}
static void ssp_request_cb(bt_bdaddr_t *remote_bd_addr, bt_bdname_t *bd_name,
--
1.7.9.5
next prev parent reply other threads:[~2013-11-08 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 12:48 [PATCH 0/8] Improve user experience Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 1/8] android/client: Export get_interface_method Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 2/8] android/client: Add NELEM macro for count elements Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 3/8] android/client: Initialize all interfaces at start Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 4/8] android/client: Add command line arguments Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 5/8] android/client: Split terminal_process_char Jerzy Kasenberg
2013-11-08 12:48 ` [PATCH 6/8] android/client: Add prompting for answer Jerzy Kasenberg
2013-11-08 12:48 ` Jerzy Kasenberg [this message]
2013-11-08 12:48 ` [PATCH 8/8] android/client: Add ssp key confirmation helper Jerzy Kasenberg
2013-11-08 13:16 ` [PATCH 0/8] Improve user experience 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=1383914910-2304-8-git-send-email-jerzy.kasenberg@tieto.com \
--to=jerzy.kasenberg@tieto.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;
as well as URLs for NNTP newsgroup(s).