From: Pascal Terjan <pterjan@mandriva.com>
To: Ron <ron@debian.org>
Cc: linux-input@vger.kernel.org, linuxwacom-devel@lists.sourceforge.net
Subject: Re: [Linuxwacom-devel] [PATCH] Use hid blacklist in usbmouse/usbkbd
Date: Mon, 26 Nov 2007 13:46:14 +0100 [thread overview]
Message-ID: <1196081174.12642.13.camel@plop> (raw)
In-Reply-To: <20071126111328.GA9235@homer.shelbyville.oz>
On lun, 2007-11-26 at 21:43 +1030, Ron wrote:
> Hi Pascal,
>
> There is a less intrusive way to handle this for any reasonably modern
> 2.6 kernel... see the check_driver script in the Debian package.
>
> It's called from udev when the device is plugged and if it is a wacom
> tablet, it will repossess it from any other driver and bind it to the
> wacom one.
>
> We had a more brutal hack that did this for 2.4 too, but this method
> is I believe the recommended one now (or at least supported without
> further kernel patching since about 2.6.13-ish).
Yes this can be workarounded in userspace, but why having a blacklist in
HID if the individual usbhid drivers still take the device ? And why
having a driver to handle a device when a better one exists ?
--
Pascal Terjan
Ingénieur Conseil
Mandriva (ex Mandrakesoft)
Tel +33 (0) 1 40 41 17 51 - Fax +33 (0) 1 40 41 92 00
-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-26 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 10:58 [PATCH] Use hid blacklist in usbmouse/usbkbd Pascal Terjan
2007-11-26 11:13 ` [Linuxwacom-devel] " Ron
2007-11-26 12:46 ` Pascal Terjan [this message]
2007-11-26 14:04 ` Ron
2007-11-26 12:50 ` Jiri Kosina
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=1196081174.12642.13.camel@plop \
--to=pterjan@mandriva.com \
--cc=linux-input@vger.kernel.org \
--cc=linuxwacom-devel@lists.sourceforge.net \
--cc=ron@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.