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.
Cl<
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.)
Helge Hafting
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).
Cl<
>
> Helge Hafting
On Tue, Jun 15, 2004 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).
>
Well, kind of... Helge Hafting is 100% correct in 2.6 sense where all
input devices have been switched to use input core. In 2.4 only USB input
devices use input core while other devices (like PS/2 mouse) use legacy
interfaces like /dev/psaux.
So for 2.4 you need to enable HID to turn on hardware driver for HID
devices and you want to enable input core to allow data from your USB
device to be awailabe to userspace.
Dmitry
> >
> > 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).
> >
>
> Well, kind of... Helge Hafting is 100% correct in 2.6 sense where all
> input devices have been switched to use input core. In 2.4 only USB input
> devices use input core while other devices (like PS/2 mouse) use legacy
> interfaces like /dev/psaux.
>
> So for 2.4 you need to enable HID to turn on hardware driver for HID
> devices and you want to enable input core to allow data from your USB
> device to be awailabe to userspace.
So that enabling HID without input core in 2.4 doesn't make sense
and enabling input core without HID in 2.4 doesn't make sense too?
Cl<
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