From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Running "putkey" for keyboards and mice
Date: Mon, 06 Sep 2010 11:06:53 +0100 [thread overview]
Message-ID: <1283767613.7529.6.camel@localhost.localdomain> (raw)
Heya,
Did a small test this week-end on my Macbook, and running "hciconfig"
with putkey works, adding the just paired keyboards' linkkey into the
Bluetooth adapter.
This meant that even though I paired the device in Linux, it was still
available in MacOS X, without any more pairing.
My question is whether we should, for all the adapters listed in the
hid2hci rules, copy the linkkeys for keyboards and (paired) mice[1] to
the adapter itself.
How would you like to see this implemented? Would a device plugin be
good enough to track newly paired devices?
Cheers
[1]: Just the mice that would require pairing, obviously, such as the
Apple mice
next reply other threads:[~2010-09-06 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 10:06 Bastien Nocera [this message]
2010-09-06 11:51 ` Running "putkey" for keyboards and mice Luiz Augusto von Dentz
2010-09-06 12:19 ` Bastien Nocera
2010-09-06 16:42 ` Bastien Nocera
2010-09-22 11:33 ` 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=1283767613.7529.6.camel@localhost.localdomain \
--to=hadess@hadess.net \
--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).