linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: linux-bluetooth@vger.kernel.org
Subject: Add empty udev rule to disable hid2hci by default
Date: Sun, 01 Dec 2013 18:26:43 +0100	[thread overview]
Message-ID: <529B7153.2060204@ahsoftware.de> (raw)

Hello.

Almost every distribution gets it wrong and enables hid2hci by default 
(besides Fedora where I already intervened twice).

This is a real problem, because it disables Bluetooth keyboards and/or 
mice which aren't paired with bluez, thus many Live-CDs and default 
installs aren't usable when only a Bluetooth keyboard is connect.

An easy solution to disable that behaviour would be to install an empty 
rule in /etc/udev/rules.d named the same as the one in 
/lib/udev/rules.d. It could just contain a comment like

# Delete this file in order to activate hid2hci.
#
# You might need to pair your Bluetooth keyboard and/or mouse
# in order to still use it when hid2hci is enabled.

This (empty) rule would then be used by udev instead of the one in 
/lib/udev/rules.d and thus would be an easy to use configuration switch.

I would appreciate it, if the default bluez install would install such 
an empty rule too, if configure was called with --enable-hid2hci.

I think otherwise that problem will never go away. It's really 
unbelievable how many distributions got this wrong and thus how many 
Live-CDs and default installations are unusable when only a Bluetooth 
keyboard is used with a hid-aware Bluetooth dongle.

Regards,

Alexander Holler

             reply	other threads:[~2013-12-01 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 17:26 Alexander Holler [this message]
2013-12-02 23:15 ` Add empty udev rule to disable hid2hci by default Alexander Holler

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=529B7153.2060204@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --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).