> > 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:30 EST