mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Andries Brouwer <aebr@win.tue.nl>,
	A Guy Called Tyketto <tyketto@wizard.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kbd not functioning in 2.5.25-dj2
Date: Sun, 14 Jul 2002 19:32:36 +0200	[thread overview]
Message-ID: <20020714193236.A27798@ucw.cz> (raw)
In-Reply-To: <200207141336.PAA01395@cave.bitwizard.nl>; from R.E.Wolff@BitWizard.nl on Sun, Jul 14, 2002 at 03:36:20PM +0200

On Sun, Jul 14, 2002 at 03:36:20PM +0200, Rogier Wolff wrote:

> Vojtech Pavlik wrote:
> > > > > mice: PS/2 mouse device common for all mice
> > > > > atkbd.c: Sent: f5
> > > > > atkbd.c: Received fe
> > > > > serio: i8042 KBD port at 0x60,0x64 irq 1
> [...]
> > Responses:
> > 
> > 0xfe
> >   Resend. Keyboard will send this if it didn't receive the last command
> > correctly.
> > 
> > Unfortunately, 0xfe also happens when you send a command to a keyboard
> > that's not plugged, or when the keyboard doesn't understand the command.
> > Resending in those cases (which are the most common) would cause an
> > infinite loop ...
> 
> Not if implemented correctly. 
> 
> Set the retry counter to 5 at the beginning. 
> 
>     if you get 0xfe: decrement retry counter, 
> 	if 0 : 
> 	    no keyboard connected. Give up. 
> 	else 
> 	    Just immediately resend the last command
>     else
> 	set the retry counter to 5 again. 
> 	process returned code

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.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-07-14 17:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13  7:24 Ed Sweetman
2002-07-13  7:37 ` A Guy Called Tyketto
2002-07-13  8:01   ` Ed Sweetman
2002-07-13  8:45     ` Ed Sweetman
2002-07-13  9:06       ` Vojtech Pavlik
2002-07-13 21:48         ` A Guy Called Tyketto
2002-07-14  8:05           ` Vojtech Pavlik
2002-07-14 10:18             ` A Guy Called Tyketto
2002-07-14 10:32               ` Russell King
2002-07-14 12:01               ` Vojtech Pavlik
2002-07-14 12:17                 ` Andries Brouwer
2002-07-14 12:37                   ` Vojtech Pavlik
2002-07-14 13:36                     ` Rogier Wolff
2002-07-14 17:32                       ` Vojtech Pavlik [this message]
2002-07-14 17:49                         ` Russell King
2002-07-14 17:59                           ` Vojtech Pavlik
2002-07-14 18:07                             ` Russell King
2002-07-14 18:11                               ` Vojtech Pavlik
2002-07-14 17:37                     ` Andries Brouwer
2002-07-14 18:01                       ` Vojtech Pavlik
2002-07-14 18:13                         ` Russell King
2002-07-14 18:17                           ` Vojtech Pavlik
2002-07-15  3:53                         ` Maciej W. Rozycki
2002-07-14 21:30                 ` A Guy Called Tyketto
2002-07-15  3:00                   ` Vojtech Pavlik
2002-07-15  8:30                     ` A Guy Called Tyketto
2002-07-15  7:28         ` Alexander Hoogerhuis
2002-07-15 10:56           ` Arnd Bergmann
2002-07-15 10:06             ` Alexander Hoogerhuis
2002-07-13  9:07       ` A Guy Called Tyketto
2002-07-13  9:32         ` Vojtech Pavlik
2002-07-13  9:04   ` Russell King
2002-07-15 15:45 Rudmer van Dijk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020714193236.A27798@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tyketto@wizard.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®