From: Yi Yang <yi.y.yang@intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] bluez: correct udev rule for Dell mouse
Date: Wed, 16 Sep 2009 15:28:58 +0800 [thread overview]
Message-ID: <20090916072858.GA22262@yangyi-dev.bj.intel.com> (raw)
>From dbcfcf5dfbdef2377f64c7cd737886e31ae17615 Mon Sep 17 00:00:00 2001
From: root <root@yangyi-dev.localdomain>
Date: Wed, 16 Sep 2009 15:19:13 +0800
Subject: [PATCH] Correct rule for Dell mouse
Note: this rule should just for Dell bluetooth mouse, but it
does function for Dell general USB mouse, such as this one:
ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
We should let it just function for Dell bluetooth mouse, udev
144 and later has included rules for hid2hci
extras/hid2hci/70-hid2hci.rules which has correct one, so we
should use that one
---
scripts/bluetooth-hid2hci.rules | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/scripts/bluetooth-hid2hci.rules b/scripts/bluetooth-hid2hci.rules
index 1b231d1..eb63292 100644
--- a/scripts/bluetooth-hid2hci.rules
+++ b/scripts/bluetooth-hid2hci.rules
@@ -8,7 +8,8 @@
# 413c:8154
# 413c:8158
# 413c:8162
-ACTION=="add", ENV{ID_VENDOR}=="413c", ENV{ID_CLASS}=="mouse", ATTRS{bmAttributes}=="e0", KERNEL=="mouse*", RUN+="/usr/sbin/hid2hci --method dell -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hci"
+ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", ATTR{bInterfaceProtocol}=="02", ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", ATTRS{bmAttributes}=="e0", \
+ RUN+="hid2hci --method dell -v $attr{idVendor} -p $attr{idProduct} --mode hci"
# Logitech devices
ACTION=="add", ENV{ID_VENDOR}=="046d", ENV{ID_MODEL}=="c703" RUN+="/usr/sbin/hid2hci --method logitech -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hci"
--
1.6.0.6
next reply other threads:[~2009-09-16 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:28 Yi Yang [this message]
2009-09-16 18:31 ` [PATCH] bluez: correct udev rule for Dell mouse Mario Limonciello
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=20090916072858.GA22262@yangyi-dev.bj.intel.com \
--to=yi.y.yang@intel.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