On Mon, Jan 18, 2010 at 06:14:51PM +0100, [email protected] wrote: > > Message du 17/01/10 à 18h43 > > De : "Kevin O'Connor" <[email protected]> > > --- a/src/ps2port.c > > +++ b/src/ps2port.c > > @@ -306,6 +306,7 @@ aux_command(int command, u8 *param) > > static void > > process_ps2irq(void) > > { > > + return; > > u8 status = inb(PORT_PS2_STATUS); > > if (!(status & I8042_STR_OBF)) { > > dprintf(1, "ps2 irq but no data.\n"); > > > > Your keyboard definitely wont work after this, but I'd like to see if > > the init succeeds with it. (I think there may be a case where > > interrupts are messing with the initialization.)
init ps2port /37fce000\ Start thread |37fce000| i8042 flushed aa (status=11) |37fce000| i8042 flushed 7e (status=11) |37fce000| i8042 flushed f0 (status=11) |37fce000| i8042 flushed 7e (status=11) |37fce000| i8042 flushed 7e (status=11) |37fce000| i8042 flushed f0 (status=11) |37fce000| i8042 flushed 7e (status=11) |37fce000| ps2_recvbyte timeout |37fce000| keyboard initialized \37fce000/ End thread So, it successfully initialized the keyboard this time. Can you confirm that it reliably reports "keyboard initialized" now instead of "keyboard self test failed"? I'll put together a patch to make sure interrupts don't mess with the init process. Thanks, -Kevin -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
