From: Vojtech Pavlik <vojtech@suse.cz>
To: Wiktor <victorjan@poczta.onet.pl>
Cc: dtor_core@ameritech.net, linux-kernel@vger.kernel.org
Subject: Re: AT keyboard dead on 2.6
Date: Fri, 28 Jan 2005 21:05:12 +0100 [thread overview]
Message-ID: <20050128200512.GA3014@ucw.cz> (raw)
In-Reply-To: <41FA972F.2000604@poczta.onet.pl>
On Fri, Jan 28, 2005 at 08:49:03PM +0100, Wiktor wrote:
> Hi,
>
> >Could you please try editing drivers/input/serio/i8042.c and add
> >udelay(20) before and after calls to i8042_write_data() in
> >i8042_kbd_write() and i8042_command().
>
> of course i could, will it make kernel not detect smoked AUX port?
> (problem is solved by i8042.noaux=1 cause my hardware has smoked PS/2
> port) i would rather think about testing devices before assuming thet
> work and trying to use them (maybe not as standard kernel feature, but
> it would be nice stuff for people with self-built machines where not
> everything works). Thanks for your help
Well, the kernel tests the AUX port and it seemed OK, that's the
problem. Unfortunately it's not always possible to detect whether
there's a problem with some device.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-01-29 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 15:27 AT keyboard dead on 2.6 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
2005-01-28 20:25 ` Vojtech Pavlik
2005-01-28 20:05 ` Vojtech Pavlik [this message]
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=20050128200512.GA3014@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=victorjan@poczta.onet.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.