From: "Karel Kulhavý" <clock@twibright.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Helge Hafting vs. make menuconfig help
Date: Tue, 15 Jun 2004 17:21:29 +0000 [thread overview]
Message-ID: <20040615172129.F6843@beton.cybernet.src> (raw)
In-Reply-To: <20040615144127.GG20632@lug-owl.de>; from jbglaw@lug-owl.de on Tue, Jun 15, 2004 at 04:41:27PM +0200
> >
> > 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
Does HID means always USB?
However when disabling CONFIG_INPUT, the keyboard still works. Is a keyboard
considered a HID or nor?
> 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).
Isn't there some graphical chart (preferrably made in sodipodi ;-) ) that
describes how data are flowing inside the kernel? I have problems visualizing
this.
Cl<
>
> 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));
next prev parent reply other threads:[~2004-06-15 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 14:02 Helge Hafting vs. make menuconfig help Karel Kulhavý
2004-06-15 14:10 ` Jan-Benedict Glaw
2004-06-15 14:20 ` Karel Kulhavý
2004-06-15 14:41 ` Jan-Benedict Glaw
2004-06-15 17:21 ` Karel Kulhavý [this message]
2004-06-15 17:32 ` Jan-Benedict Glaw
2004-06-15 17:46 ` AT Keyboard (was: Helge Hafting vs. make menuconfig help) Karel Kulhavý
2004-06-15 18:37 ` Helge Hafting
2004-06-15 19:59 ` Karel Kulhavý
2004-06-15 20:13 ` Jan-Benedict Glaw
2004-06-16 22:30 ` Helge Hafting
2004-06-15 20:35 ` Helge Hafting vs. make menuconfig help Vojtech Pavlik
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=20040615172129.F6843@beton.cybernet.src \
--to=clock@twibright.com \
--cc=jbglaw@lug-owl.de \
--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 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.