On Sun, Jul 14, 2002 at 07:07:59PM +0100, Russell King wrote:
> On Sun, Jul 14, 2002 at 07:59:02PM +0200, Vojtech Pavlik wrote:
> > On Sun, Jul 14, 2002 at 06:49:54PM +0100, Russell King wrote:
> > > On Sun, Jul 14, 2002 at 07:32:36PM +0200, Vojtech Pavlik wrote:
> > > > Yes. Sure. I knew someone will suggest that. :) The only problem is,
> > > > I've never seen a keyboard sending 0xfe because it wants the command
> > > > sent again. Under normal circumstances, there aren't bit errors on the
> > > > cable.
> > >
> > > I think you missed my mail at the beginning of this thread.
> >
> > I read it. Well, let's first see where the 0xfe really comes from. :)
>
> Err, the keyboard. The hardware I saw it on was with just a plain
> PS/2 port with zero inteligence within; it's effectively a serial port
> talking direct to the keyboard.
I was talking about the one from Tyketto, yours was most likely
happening because the keyboard considered the line testing as a
beginning of a character being sent, then attached the rest of the
initial 0xf5 to it and got a nonsense. This is not exactly a bit error
on the wire.
-- Vojtech Pavlik SuSE Labs - 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 : Mon Jul 15 2002 - 22:00:28 EST