public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: dtor_core@ameritech.net
Cc: Wiktor <victorjan@poczta.onet.pl>, linux-kernel@vger.kernel.org
Subject: Re: AT keyboard dead on 2.6
Date: Fri, 28 Jan 2005 20:35:42 +0100	[thread overview]
Message-ID: <20050128193542.GA2877@ucw.cz> (raw)
In-Reply-To: <d120d5000501281127752561a3@mail.gmail.com>

On Fri, Jan 28, 2005 at 02:27:20PM -0500, Dmitry Torokhov wrote:
> On Fri, 28 Jan 2005 20:22:32 +0100, Wiktor <victorjan@poczta.onet.pl> wrote:
> > Hi,
> > 
> > >This dmesg looks like the keyboard works perfectly OK. Do new lines
> > >appear in dmesg when you press keys while the system is running?
> > 
> > eeeeeeee.....no? no, they don't. i've new dmesg for you - it reports
> > timeouts while trying to perform keyboard reset (by atkbd.reset=1).
> > after detection pressing any keys has absolutley no effect. maybe it's
> > some timeout-violation?
> > 
> 
> Could you please try editing drivers/input/serio/i8042.c and add
> udelay(20) before and after calls to i8042_write_data() in
> i8042_kbd_write() and i8042_command().
 
Uh? What that'd help? All the communication proceeds OK, up to proper
registration of the input device, but the keyboard seems to stay in a
'disabled' state. The keyboard, not the controller, because if it were
the controller, atkbd.c wouldn't get the 'fa' responses back via
functioning interrupts.

Wiktor, can you try atkbd.dumbkbd=1?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-01-29 19:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 15:27 AT keyboard dead on 2.6 Wiktor
2005-01-21 15:48 ` Dmitry Torokhov
2005-01-21 19:07   ` Wiktor
2005-01-21 19:38     ` Dmitry Torokhov
2005-01-25 19:37       ` Wiktor
2005-01-28 14:31         ` Vojtech Pavlik
2005-01-28 14:46           ` Dmitry Torokhov
2005-01-28 18:41             ` Vojtech Pavlik
2005-01-28 19:22             ` Wiktor
2005-01-28 19:27               ` Dmitry Torokhov
2005-01-28 19:35                 ` Vojtech Pavlik [this message]
2005-01-29 20:32                   ` Wiktor
2005-01-28 19:49                 ` Wiktor
2005-01-28 19:53                   ` Dmitry Torokhov
2005-01-28 20:22                     ` Wiktor
2005-01-28 20:25                       ` Vojtech Pavlik
2005-01-28 20:05                   ` Vojtech Pavlik
2005-01-28 19:27               ` Vojtech Pavlik
2005-01-29 20:29                 ` Wiktor
2005-01-28 14:28 ` Vojtech Pavlik
2005-01-28 16:47   ` Christian
2005-01-28 19:39     ` Wiktor
2005-01-28 19:41       ` Vojtech Pavlik
2005-01-29 20:38         ` Wiktor

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=20050128193542.GA2877@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=victorjan@poczta.onet.pl \
    /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