From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: bipassing USBHID driver with udev rule
Date: Mon, 27 Jul 2009 14:54:04 +0000 [thread overview]
Message-ID: <20090727145404.GA18903@kroah.com> (raw)
In-Reply-To: <644830.47374.qm@web110709.mail.gq1.yahoo.com>
On Sun, Jul 26, 2009 at 12:30:28PM -0700, vijay manchala wrote:
>
> Hi,
>
> I need some understanding regarding usbHID driver
>
> I had one device called footpedal usb device, when I connected that
> device to the HOST machine RHEL , default usbHID driver is detecting
> my footpedal i,e usbhid driver.
>
> Actually
> I dont want usbHID driver to detect foot pedal device, it would have
> been nice if there was just a nice simple way of stopping the kernel
> usbHID driver from getting in the way, I want this pedal detected by
> my own modified mouse driver.
Then just send a patch adding your device to the HID blacklist in the
driver. That will keep it from being loaded.
good luck,
greg k-h
prev parent reply other threads:[~2009-07-27 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 19:30 bipassing USBHID driver with udev rule vijay manchala
2009-07-27 14:54 ` Greg KH [this message]
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=20090727145404.GA18903@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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).