Messages in this thread | | | Date | Tue, 15 Jun 2004 16:41:27 +0200 | From | Jan-Benedict Glaw <> | Subject | Re: Helge Hafting vs. make menuconfig help |
| |
On Tue, 2004-06-15 14:20:40 +0000, Karel Kulhavý <clock@twibright.com> wrote in message <20040615142040.B6241@beton.cybernet.src>: > On Tue, Jun 15, 2004 at 04:10:39PM +0200, Jan-Benedict Glaw wrote: > > On Tue, 2004-06-15 14:02:06 +0000, Karel Kulhavý <clock@twibright.com> > > wrote in message <20040615140206.A6153@beton.cybernet.src>:
> > CONFIG_INPUT only gives you an API where you can process input events > > with. For instance, look at the atkbd.c, sunkbd.c or lkkbd.c drivers. > > They all send key strokes into the Input API (activated by > > CONFIG_INPUT), but none of them actually uses USB (but the PS/2 keyboard > > port or normal serial ports with non-standard plugs). > > Is it correct what <Help> for CONFIG_INPUT in 2.4.25 says or no?
At least, it's not really wrong. You need CONFIG_INPUT to be able to do something with the HID stuff. However, to have an uniform interface, you may also use the CONFIG_INPUT stuff to access your "normal" (AT / PS/2 style) keyboard.
In 2.6.x, that's cleaned up a bit. (Nearly?) all keyboards now push their key strokes into the CONFIG_INPUT API, so you really want to have CONFIG_INPUT (as long as this isn't some kind of embedded system).
MfG, JBG
-- Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); [unhandled content-type:application/pgp-signature] | |