public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Hal Duston <hald@sound.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input w/2.5.3-dj3
Date: Fri, 8 Feb 2002 08:17:08 +0100	[thread overview]
Message-ID: <20020208081708.A2995@suse.cz> (raw)
In-Reply-To: <Pine.GSO.4.10.10202071151580.16311-100000@sound.net>
In-Reply-To: <Pine.GSO.4.10.10202071151580.16311-100000@sound.net>; from hald@sound.net on Thu, Feb 07, 2002 at 11:55:19AM -0600

On Thu, Feb 07, 2002 at 11:55:19AM -0600, Hal Duston wrote:

> OK, I have checked my config.  The only item I was missing
> was CONFIG_KEYBOARD_XTKBD=y.

You had it all then - CONFIG_KEYBOARD_XTKBD isn't needed.

> I have now added that, and 
> still no keyboard activity.  This is a laptop from 1994
> or so, so it's not exactly new stuff.

The old stuff and namely laptops is the most crazy where it comes to
compatibility in the keyboard area. So it may be the code fails for some
reason on your laptop.

> What should I check next?

Can you please enable #define I8042_DEBUG_IO in i8042.h and ATKBD_DEBUG
in atkbd.c, recompile, and send me the relevant 'dmesg' of your boot
with the -dj kernel?

I'll try to fix the problem then.

Thanks.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-08  7:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 17:55 Input w/2.5.3-dj3 Hal Duston
2002-02-08  7:17 ` Vojtech Pavlik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 19:24 Hal Duston
2002-02-15  0:22 ` Vojtech Pavlik
2002-02-12  1:00 Hal Duston
2002-02-12  9:00 ` Vojtech Pavlik
2002-02-11 20:39 Hal Duston
2002-02-11 20:55 ` Vojtech Pavlik
2002-02-11 17:56 Hal Duston
2002-02-11 17:58 ` Vojtech Pavlik
2002-02-08 19:12 Hal Duston
2002-02-09 17:00 ` Vojtech Pavlik
2002-02-07 16:43 Hal Duston
2002-02-07 16:51 ` Dave Jones

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=20020208081708.A2995@suse.cz \
    --to=vojtech@suse.cz \
    --cc=hald@sound.net \
    --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