linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolai Kondrashov <spbnick@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH 1/1] HID: add have_special_driver hid module parameter
Date: Thu, 29 Mar 2012 11:00:42 +0300	[thread overview]
Message-ID: <4F7416AA.1070704@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1202281527250.31150@pobox.suse.cz>

Hi Jiri,

On 02/28/2012 04:30 PM, Jiri Kosina wrote:
> On Mon, 27 Feb 2012, Nikolai Kondrashov wrote:
>
>>> Add "have_special_driver" hid module parameter - a list of additional
>>> HID devices which have specialized driver on HID bus. Needed to
>>> support out-of-tree HID drivers.
>>
>> Did you have time to take a look at the patch?
>> If there's anything wrong with it, please tell me and I'll fix it.
>
> Hi Nikolai,
>
> well, I am not really sure what value does it provide to have such
> functionality in the kernel.

In addition to my other explanations, I know about 10 people who are using
my tablet drivers which are to be included into the 3.4 release. And these
are only those who contacted me. Now, they can't be helped, they will have
to build their own kernels until they can install an official one with the
drivers.

However, there are still many unsupported tablets and other devices which
could be made to work with a simple HID driver. If this or a similar
functionality is there, they will need to only build and install a few
modules, or just install a DKMS-enabled package for their distribution.
And the sooner that happens, the better.

I understand that this solution is somewhat hackish, but it matches the
generic HID driver's ignoring of devices. The only proper solution,
considering asynchronous module loading, would be to bind the generic HID
driver to all HID devices unconditionally and then rebind a specific driver
once it's loaded. Yet, I'm not sure how this would fit the device driver
model.

Thank you for your attention and sorry if I bother you unnecessarily :)

Sincerely,
Nick

  parent reply	other threads:[~2012-03-29  8:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 21:29 [PATCH 1/1] HID: add have_special_driver hid module parameter Nikolai Kondrashov
2012-02-27 14:15 ` Nikolai Kondrashov
2012-02-28 14:30   ` Jiri Kosina
2012-02-28 15:12     ` Nikolai Kondrashov
2012-02-29 21:23     ` Nikolai Kondrashov
2012-03-29  8:00     ` Nikolai Kondrashov [this message]
2012-03-30 13:49 ` Jiri Kosina
2012-03-30 15:22   ` Nikolai Kondrashov
2012-03-30 23:03     ` David Herrmann
2012-04-01 19:44       ` Nikolai Kondrashov
2012-04-01 19:49         ` Jiri Kosina
2012-04-01 20:11           ` Nikolai Kondrashov
2012-04-01 20:10         ` David Herrmann
2012-04-01 20:22           ` Nikolai Kondrashov
2012-04-01 19:33   ` Nikolai Kondrashov
2012-04-01 19:46     ` Jiri Kosina
2012-04-01 20:50       ` Nikolai Kondrashov
2012-04-02 23:41         ` Jiri Kosina
2012-04-04  8:27           ` Nikolai Kondrashov
2012-04-08 10:48           ` Nikolai Kondrashov
2012-04-03 14:46         ` Henrik Rydberg
2012-04-03 15:09           ` Jiri Kosina
2012-04-03 16:37             ` Henrik Rydberg
2012-04-03 17:01               ` Jiri Kosina
2012-04-03 17:11                 ` Henrik Rydberg

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=4F7416AA.1070704@gmail.com \
    --to=spbnick@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@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).