mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 CONFIG_INPUT_KEYBDEV
Date: Tue, 11 Oct 2005 06:50:01 +0200	[thread overview]
Message-ID: <20051011045001.GH22601@alpha.home.local> (raw)
In-Reply-To: <200510101924.02560.nick@linicks.net>

On Mon, Oct 10, 2005 at 07:24:02PM +0100, Nick Warne wrote:
> On Sunday 09 October 2005 21:40, Willy Tarreau wrote:
> 
> > > Oct  9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
> > > Oct  9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
> >
> > (...)
> >
> > > Therefore I still have to manually edit include/linux/pc_keyb.h to undef
> > > the (no) keyboard timeouts:
> >
> > This option is not used for pc_keyb.c inclusion which is linked unless you
> > set CONFIG_DUMMY_KEYB (check drivers/char/Makefile for this), in which case
> > you'll use dummy_keyb.c which was made exactly for your usage.
> 
> OK, thanks, but I am still confused.  I had to add CONFIG_DUMMY_KEYB=y 
> manually (i386), as nowhere could I find an option in menuconfig (and 
> find/grep revealed nothing either)...
> 
> This now boots with no keyboard warnings, as suggested (after I removed keymap 
> etc. from start scripts).  But I still think I done it all wrong?

Not necessarily, it may be that too few people use it and the option has
vanished from any config. You can provide a patch to re-enable it if you
want. In this case, please also provide a little help in Configure.help.

Regards,
Willy


      reply	other threads:[~2005-10-11  4:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09 10:41 Nick Warne
2005-10-09 20:00 ` Valdis.Kletnieks
2005-10-09 20:40 ` Willy Tarreau
2005-10-10 18:24   ` Nick Warne
2005-10-11  4:50     ` Willy Tarreau [this message]

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=20051011045001.GH22601@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    /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®