From: Ivan Ukhov <uvsoft@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: UVSoft@gmail.com
Subject: Re: How to use an usb interface than is claimed by HID?
Date: Sun, 21 Jan 2007 11:59:44 +0300 [thread overview]
Message-ID: <45B32B80.4050208@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701210050490.21127@twin.jikos.cz>
> Could I ask you what precisely is the driver you are talking about doing?
> Why is it not going to be a part of mainline kernel (i.e. being able to be
> put on blacklist easily).
>
It's a tiny driver and it hardy can be a part of the mainline kernel
because of its useless for everyone but me, beside I don't want to make
someone modify the kernel code. For example, I've written this driver,
than someone who wanna use it takes the code and tries to deal with it
and he finds out that he also needs to have the latest kernel (where the
device is included to that black list) or to fix the kernel himself.
It's rather uncomfortable for a person who just wants to use a simple
device with a simple driver, isn't it? It'll be great if my driver can
manage it himself.
> Sure, there are such in-kernel drivers ... for example Wacom driver. This
> driver is in-kernel, and it is hooked inside the usb_hid_configure()
> function to be ignored by the HID layer completely, and all the driver
> specific handling is handled in drivers/usb/input/wacom*.
>
> (When looking at that code, it looks quite ugly by the way. I have no idea
> why wacom driver is not using HID_QUIRK_IGNORE, but has a hardcoded hook
> in the usb_hid_configure() instead. I will probably fix this.)
>
As far as I remember this driver modifies the HID driver... it's what I
was talking about late.
next prev parent reply other threads:[~2007-01-21 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 18:56 How to use an usb interface than is claimed by HID? Ivan Ukhov
2007-01-20 23:09 ` Jiri Kosina
2007-01-20 23:47 ` Ivan Ukhov
2007-01-20 23:56 ` Jiri Kosina
2007-01-21 8:59 ` Ivan Ukhov [this message]
2007-01-21 13:01 ` Jiri Kosina
2007-01-21 14:01 ` Ivan Ukhov
2007-01-21 17:28 ` Jiri Kosina
2007-01-21 18:34 ` Ivan Ukhov
2007-01-23 12:57 ` Rolf Offermanns
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=45B32B80.4050208@gmail.com \
--to=uvsoft@gmail.com \
--cc=linux-kernel@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