From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Felipe Tonello <eu@felipetonello.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Eric Curtin <ericcurtin17@gmail.com>,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with printk logs and my driver
Date: Fri, 25 Sep 2015 11:45:38 -0400 [thread overview]
Message-ID: <56056C22.7050807@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1509251400320.30132@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
On 2015-09-25 08:02, Jiri Kosina wrote:
> On Fri, 25 Sep 2015, Felipe Tonello wrote:
>
>> Maybe a better description on Kconfig and/or comments on source code
>> it's enough.
>
> I personally find the current Kconfig description:
>
> ===
> config USB_KBD
> tristate "USB HIDBP Keyboard (simple Boot) support"
> depends on USB && INPUT
> ---help---
> Say Y here only if you are absolutely sure that you don't want
> to use the generic HID driver for your USB keyboard and prefer
> to use the keyboard in its limited Boot Protocol mode instead.
>
> This is almost certainly not what you want. This is mostly
> useful for embedded applications or simple keyboards.
>
> To compile this driver as a module, choose M here: the
> module will be called usbkbd.
>
> If even remotely unsure, say N.
> ===
>
> shouldn't leave anyone dounting, but people are getting confused again and
> again nevertheless.
>
For some reason there seem to be a lot of people who go to configure
there own kernel and don't read the help text (I understand if you've
been building your own Linux kernel's for years and actually understand
what a Kconfig option is really asking, but most people who I've heard
of doing this have never built a kernel before in their life).
On the other hand, can anyone think of any real reason to use this
outside of embedded systems? I know there are a lot of distros that
build this and the USB HIDBP mouse support as modules, but I have yet to
hear/find any reports of hardware that _only_ works with this driver and
not the generic HID driver. If this is the case, it might make sense to
make this depend on EXPERT or at least remove the bit about 'simple
keyboards'.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-25 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 23:44 Problems with printk logs and my driver Eric Curtin
2015-09-24 0:38 ` Alan Stern
2015-09-24 5:49 ` Jiri Kosina
2015-09-24 20:51 ` Alan Stern
2015-09-25 10:05 ` Felipe Tonello
2015-09-25 12:02 ` Jiri Kosina
2015-09-25 15:45 ` Austin S Hemmelgarn [this message]
2015-09-29 22:11 ` Eric Curtin
2015-09-30 12:07 ` Austin S Hemmelgarn
2015-10-04 12:31 ` Eric Curtin
2015-10-04 15:28 ` Alan Stern
2015-10-14 22:33 ` Eric Curtin
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=56056C22.7050807@gmail.com \
--to=ahferroin7@gmail.com \
--cc=ericcurtin17@gmail.com \
--cc=eu@felipetonello.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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