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: Wed, 29 Feb 2012 23:23:36 +0200 [thread overview]
Message-ID: <4F4E9758.9020908@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1202281527250.31150@pobox.suse.cz>
On 02/28/2012 04:30 PM, Jiri Kosina wrote:
> well, I am not really sure what value does it provide to have such
> functionality in the kernel.
>
> I can understand that it helps you when developing out-of-tree (yet)
> drivers ... but as you are patching the kernel anyway with those drivers,
> you can easily run a kernel that has hid_have_special_driver[] array
> adjusted accordingly. And once you are submitting the driver for
> inclusion, you are of course submitting it together with
> hid_have_special_driver[] addition.
>
> So it doesn't seem to be a debugging facility to me, and neither does it
> provide any added value for users of vanilla kernel.
Maybe I did too extensive an explanation. Here is a shorter one.
This is not needed for development, but only for end users to be able to
load an out-of-tree driver before it becomes available in their
distribution.
Without this, they will need to build their own kernel with my patches every
time it is updated.
With this, they will even be able to use DKMS to have drivers built and
installed automatically with each kernel update.
My rationalization for this specific solution:
http://thread.gmane.org/gmane.linux.usb.general/58661/focus=58869
Sincerely,
Nick
next prev parent reply other threads:[~2012-02-29 21:23 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 [this message]
2012-03-29 8:00 ` Nikolai Kondrashov
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=4F4E9758.9020908@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 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.