linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@netsplit.com>
To: linux-bluetooth@vger.kernel.org
Cc: keybuk@chromium.org, Scott James Remnant <scott@netsplit.com>
Subject: [PATCHv2 0/8] Generate PIN for keyboards inside bluetoothd
Date: Mon, 23 Jan 2012 16:27:44 -0800	[thread overview]
Message-ID: <1327364872-32313-1-git-send-email-scott@netsplit.com> (raw)

Thanks for the comments on my RFC patch set, I've addressed those in
this new version which I'm now submitting formally.

The main changes are:
 - bt_ids.h moved to src/
 - a D-Bus error from calling DisplayPinCode results in a fallback to
   calling RequestPinCode instead
 - PIN isn't sent to the adapter until a successful reply from either
   DisplayPinCode or RequestPinCode

This grew the patch a bit unsurprisingly, so I've split it up a fair
amount more - including separating out the documentating and tests
as requested.

Scott James Remnant (8):
  bt_ids: add header of device class constants
  Rename AUTH_TYPE_NOTIFY to AUTH_TYPE_NOTIFY_PASSKEY
  Pass passkey by pointer rather than by value
  agent: add DisplayPinCode method
  Add AUTH_TYPE_NOTIFY_PASSKEY to device_request_authentication
  Generate PIN for keyboard devices
  doc: document DisplayPinCode
  simple-agent: add DisplayPinCode

 doc/agent-api.txt |   24 ++++++++++
 src/agent.c       |  112 +++++++++++++++++++++++++++++++++++++++++++++++-
 src/agent.h       |    4 ++
 src/bt_ids.h      |  125 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 src/device.c      |   72 +++++++++++++++++++++++++++---
 src/device.h      |    5 +-
 src/event.c       |   29 ++++++++++--
 test/simple-agent |    5 ++
 8 files changed, 360 insertions(+), 16 deletions(-)
 create mode 100644 src/bt_ids.h

-- 
1.7.7.3


             reply	other threads:[~2012-01-24  0:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  0:27 Scott James Remnant [this message]
2012-01-24  0:27 ` [PATCHv2 1/8] bt_ids: add header of device class constants Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 2/8] Rename AUTH_TYPE_NOTIFY to AUTH_TYPE_NOTIFY_PASSKEY Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 3/8] Pass passkey by pointer rather than by value Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 4/8] agent: add DisplayPinCode method Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 5/8] Add AUTH_TYPE_NOTIFY_PASSKEY to device_request_authentication Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 6/8] Generate PIN for keyboard devices Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 7/8] doc: document DisplayPinCode Scott James Remnant
2012-01-24  0:27 ` [PATCHv2 8/8] simple-agent: add DisplayPinCode Scott James Remnant

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=1327364872-32313-1-git-send-email-scott@netsplit.com \
    --to=scott@netsplit.com \
    --cc=keybuk@chromium.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).