> Date: Sun, 27 Jul 2003 12:47:26 +0200
> From: Andries Brouwer <aebr@win.tue.nl>
> So the culprit is the failing of atkbd_probe().
> It does a ATKBD_CMD_GETID, but gets no answer, then a
> ATKBD_CMD_SETLEDS, and that command fails.
I see the light now. Somehow I imagined that atkbd code does not call
the ->open for the port. Now it all falls into place. Everything works
with a bigger timeout.
Thanks a lot, Andries & Chris!
-- Pete
diff -urN -X dontdiff linux-2.6.0-test1-bk2/drivers/input/keyboard/atkbd.c linux-2.6.0-test1-bk2-nip/drivers/input/keyboard/atkbd.c
--- linux-2.6.0-test1-bk2/drivers/input/keyboard/atkbd.c 2003-07-13 20:37:15.000000000 -0700
+++ linux-2.6.0-test1-bk2-nip/drivers/input/keyboard/atkbd.c 2003-07-27 15:20:35.000000000 -0700
@@ -214,7 +214,7 @@
static int atkbd_sendbyte(struct atkbd *atkbd, unsigned char byte)
{
- int timeout = 10000; /* 100 msec */
+ int timeout = 20000; /* 200 msec */
atkbd->ack = 0;
#ifdef ATKBD_DEBUG
-
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:34 EST