linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Heath <chris@heathens.co.nz>
To: aebr@win.tue.nl
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: i8042 problem
Date: Sat, 26 Jul 2003 21:41:32 -0400	[thread overview]
Message-ID: <20030726212513.A0BD.CHRIS@heathens.co.nz> (raw)
In-Reply-To: <20030726093619.GA973@win.tue.nl>

> > drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [40] 
> > drivers/input/serio/i8042.c: 60 -> i8042 (command) [50] 
> > drivers/input/serio/i8042.c: 44 -> i8042 (parameter) [50] 
> > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [51] 
> > serio: i8042 KBD port at 0x60,0x64 irq 1 
> > <------------- This is it, keyboard is dead. 
> 
> 
> Writing 44 to the command byte disables IRQ1. 

It looks like a timeout problem.  The ack (fa) arrived 11 ticks after
the byte (00) was sent, but it looks like the timeout is only 10 ticks.

Try playing with the timeout in atkbd_sendbyte (line 217 of
drivers/input/keyboard/atkbd.c).


> > drivers/input/serio/i8042.c: 41 <- i8042 (interrupt, kbd, 1) [109900] 
> > drivers/input/serio/i8042.c: 41 <- i8042 (interrupt, kbd, 1) [109921] 
> > atkbd.c: Unknown key (set 0, scancode 0x2, on isa0060/serio0) pressed. 
> > input: AT Set 2 keyboard on isa0060/serio0 
> > <----- Now we are talking! 
> 
> 
> Funny. Looks like the "read scancode set" command got the scancode set 
> twice, and the second time was seen as unknown key. 

Both keyboards responded to the command, perhaps???

I'd suggest that we don't even ask the keyboard what scancode set it is
using if we are attempting to use set 2.

Chris


  reply	other threads:[~2003-07-27  1:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26  6:11 i8042 problem Pete Zaitcev
2003-07-26  9:36 ` Andries Brouwer
2003-07-27  1:41   ` Chris Heath [this message]
2003-07-27  6:06     ` Pete Zaitcev
2003-07-27 10:47       ` Andries Brouwer
2003-07-28  1:55         ` Pete Zaitcev
2003-07-28 11:25           ` Alan Cox
2003-07-28 11:59             ` Andries Brouwer
2003-07-28 14:01               ` Maciej W. Rozycki
2003-07-28 14:54                 ` Andries Brouwer
2003-07-28 15:43                   ` Maciej W. Rozycki
2003-07-28 15:51                     ` Andries Brouwer
2003-07-29 18:29                       ` Maciej W. Rozycki
2003-08-12 20:46                         ` Vojtech Pavlik
2003-08-13 13:44                           ` Maciej W. Rozycki
2003-07-28 16:07             ` Pete Zaitcev
2003-08-12 20:47               ` Vojtech Pavlik
2003-08-12 20:42         ` Vojtech Pavlik
2003-08-12 23:06           ` Andries Brouwer

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=20030726212513.A0BD.CHRIS@heathens.co.nz \
    --to=chris@heathens.co.nz \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).