mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wiktor <victorjan@poczta.onet.pl>
To: dtor_core@ameritech.net
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: AT keyboard dead on 2.6
Date: Fri, 28 Jan 2005 21:22:20 +0100	[thread overview]
Message-ID: <41FA9EFC.9040600@poczta.onet.pl> (raw)
In-Reply-To: <d120d50005012811534eb1ed70@mail.gmail.com>

Hi,

> We do test AUX port and your port appears to be perfectly functional
> from the kernel point of view - it porperly responds to AUX_LOOP
> commands, does not claim to support MUX mode and KBC properly sets
> status register when asked to disable interface...

ok, but how AUX block KBD port? if procesor-interface works, it 
shouldn't disturb communication in any way! how it is possible that 
tests do not detect broken down port? if kernel enables it in some way 
(when disabling port from command line, KBD works ok), it should be 
detected that AUX does not work correctly and lock it somehow? can it be 
etermined by analyzing data flow? or maybe tests are not enought good, 
maybe some corelations when using both KBD and AUX exist and are not 
tested? as my keyboard works now, i'm not keen on solving this, but to 
make the world better and dominate it, some "runtime hardware failures 
handling" could be added.

--
May the Source be with you.
wixor

  reply	other threads:[~2005-01-28 20:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 15:27 Wiktor
2005-01-21 15:48 ` Dmitry Torokhov
2005-01-21 19:07   ` Wiktor
2005-01-21 19:38     ` Dmitry Torokhov
2005-01-25 19:37       ` Wiktor
2005-01-28 14:31         ` Vojtech Pavlik
2005-01-28 14:46           ` Dmitry Torokhov
2005-01-28 18:41             ` Vojtech Pavlik
2005-01-28 19:22             ` Wiktor
2005-01-28 19:27               ` Dmitry Torokhov
2005-01-28 19:35                 ` Vojtech Pavlik
2005-01-29 20:32                   ` Wiktor
2005-01-28 19:49                 ` Wiktor
2005-01-28 19:53                   ` Dmitry Torokhov
2005-01-28 20:22                     ` Wiktor [this message]
2005-01-28 20:25                       ` Vojtech Pavlik
2005-01-28 20:05                   ` Vojtech Pavlik
2005-01-28 19:27               ` Vojtech Pavlik
2005-01-29 20:29                 ` Wiktor
2005-01-28 14:28 ` Vojtech Pavlik
2005-01-28 16:47   ` Christian
2005-01-28 19:39     ` Wiktor
2005-01-28 19:41       ` Vojtech Pavlik
2005-01-29 20:38         ` Wiktor

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=41FA9EFC.9040600@poczta.onet.pl \
    --to=victorjan@poczta.onet.pl \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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

Powered by JetHome