On Sun, 28 Jun 2009, Dr. David Alan Gilbert wrote: > Apologies for the delay; attached is the dmesg from the Debian 2.6.18 > in which keyboard works as previously described. So the main difference is here: drivers/input/serio/i8042.c: 20 -> i8042 (command) [3] drivers/input/serio/i8042.c: 65 <- i8042 (return) [3] drivers/input/serio/i8042.c: 60 -> i8042 (command) [3] drivers/input/serio/i8042.c: 74 -> i8042 (parameter) [3] drivers/input/serio/i8042.c: Interrupt 1, without any data [3] compared to drivers/input/serio/i8042.c: 20 -> i8042 (command) [1] drivers/input/serio/i8042.c: 65 <- i8042 (return) [1] drivers/input/serio/i8042.c: 60 -> i8042 (command) [2] drivers/input/serio/i8042.c: 74 -> i8042 (parameter) [2] drivers/input/serio/i8042.c: d3 -> i8042 (command) [2] So it looks like it is really affected by the polling timer removal/early IRQ registration. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
