From: Vojtech Pavlik <vojtech@suse.cz>
To: "Karel Kulhavý" <clock@twibright.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
linux-kernel@vger.kernel.org,
Lubomir Prech <Lubomir.Prech@mff.cuni.cz>
Subject: Re: HID vs. Input Core
Date: Tue, 15 Jun 2004 20:07:38 +0200 [thread overview]
Message-ID: <20040615180738.GA2200@ucw.cz> (raw)
In-Reply-To: <20040615135605.B6090@beton.cybernet.src>
On Tue, Jun 15, 2004 at 01:56:05PM +0000, Karel Kulhavý wrote:
> On Tue, Jun 15, 2004 at 03:41:53PM +0200, Helge Hafting wrote:
> > On Tue, Jun 15, 2004 at 12:58:00PM +0000, Karel Kulhavý wrote:
> > > Hello
> > >
> > > I would like to know what's the difference between
> > > Input Core (CONFIG_INPUT) and USB HID (CONFIG_USB_HID) in 2.4.25
> > >
> > > They seem to enable the same thing - USB HID. However I don't
> > > know which one should I enable or if I should enable both. I find
> > > existence of two options with seemingly the same function confusing.
> > >
> > They aren't the same:
> >
> > Enable CONFIG_INPUT if you want to use any input devices _at all_,
> > i.e. if you plan on using some kind of keyboard, mouse, joystick, ...
> > Enable CONFIG_USB_HID also, _if_ such a device might be connected
> > via USB. (Older devices are not USB, newer may be usb.)
>
> Bugreport:
>
> CONFIG_INPUT Help says
> "Say Y here if you want to enable any of the following options for USB
> Human Interface Device (HID) support".
>
> Helge Hafting from linux-kernel says that CONFIG_INPUT controls enabling input devices at
> all. These two statements are in a direct contradiction. (See above).
In 2.4 the only devices (well, except joysticks) using the input core
are USB HID devices.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-06-15 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 12:58 Karel Kulhavý
2004-06-15 13:41 ` Helge Hafting
2004-06-15 13:56 ` Karel Kulhavý
2004-06-15 18:07 ` Vojtech Pavlik [this message]
2004-06-15 14:35 Dmitry Torokhov
2004-06-15 17:22 ` Karel Kulhavý
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=20040615180738.GA2200@ucw.cz \
--to=vojtech@suse.cz \
--cc=Lubomir.Prech@mff.cuni.cz \
--cc=clock@twibright.com \
--cc=helgehaf@aitel.hist.no \
--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
all inboxes | Powered by JetHome®