From: Peter Hurley <peter@hurleysoftware.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "martin.pitt@ubuntu.com" <martin.pitt@ubuntu.com>
Subject: Bluez needs configuration mechanism for not running hid2hci
Date: Fri, 3 Jun 2011 17:18:44 -0400 [thread overview]
Message-ID: <1307135924.2622.109.camel@THOR> (raw)
Related to my earlier patch for the udev rules here
<http://marc.info/?l=linux-bluetooth&m=130713440317947&w=2>,
Bluez needs a configurable way of *NOT* running hid2hci.
Currently, if a device *is capable* of switching to HCI mode, it _is_
switched to HCI mode. There are several problems with this approach:
1. Multi-boot systems. Since each host OS currently has different link
keys (or if the host names are different), *on each cross-boot*
bluetooth devices must be re-paired.
2. Input devices. Currently, after hid2hci switches modes, there is no
reliable way to pair input devices *without non-bluetooth input
devices*. This means that users with access to bluetooth keyboard and
mouse *only* should leave those devices in HID mode.
Pre-udev, /etc/bluetooth/main.conf had HID2HCI_ENABLE= to enable/disable
this behavior.
Now, there's nothing - and this is the source of *a lot* of distro bug
reports. Here's a spattering from Ubuntu only:
https://bugs.launchpad.net/ubuntu/lucid/+source/udev/+bug/444420
https://bugs.launchpad.net/ubuntu/lucid/+source/udev/+bug/550288
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/658471
The solutions people come up with is to, in-essence, blacklist HCI mode
for other users!
Ideas?
Regards,
Peter Hurley
reply other threads:[~2011-06-03 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1307135924.2622.109.camel@THOR \
--to=peter@hurleysoftware.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
/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).