From: Stefan Smietanowski <stesmi@stesmi.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Vojtech Pavlik <vojtech@suze.cz>,
torvalds@osdl.org, vojtech@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 24/44] Workaround i8042 chips with broken MUX mode
Date: Sun, 28 Mar 2004 09:45:58 +0200 [thread overview]
Message-ID: <406682B6.4030505@stesmi.com> (raw)
In-Reply-To: <200403271940.39940.dtor_core@ameritech.net>
Hi.
> linked to broken legacy emulation implementations, Vojtech mentioned
> that PCI quirk to turn legacy emulation off may be appropriate.
Is there any code available that can do that as it is now?
This would be useful especially right now under x86-64.
As it is right now I either have the keyboard plugged into
both ps/2 and usb, plug it in only into usb (can't operate
grub) or plug it only into usb (enable emulation, can't
run linux ... ) and if the kernel could have a way of
disabling the emulation that would be good at least in
my case.
// Stefan
next prev parent reply other threads:[~2004-03-28 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 18:24 [PATCH 24/44] Workaround i8042 chips with broken MUX mode Dmitry Torokhov
2004-03-18 20:37 ` Vojtech Pavlik
[not found] ` <200403190005.36956.dtor_core@ameritech.net>
2004-03-19 13:58 ` Vojtech Pavlik
2004-03-19 14:21 ` Stefan Smietanowski
2004-03-19 14:30 ` Vojtech Pavlik
2004-03-19 13:56 ` Vojtech Pavlik
2004-03-28 0:29 ` Andries Brouwer
2004-03-28 0:40 ` Dmitry Torokhov
2004-03-28 1:25 ` Andries Brouwer
2004-03-28 3:11 ` Dmitry Torokhov
2004-03-28 7:45 ` Stefan Smietanowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 14:19 [PATCH 23/44] Use __obsolete_setup() in input drivers to warn about obsolete kernel params Vojtech Pavlik
2004-03-16 14:19 ` [PATCH 24/44] Workaround i8042 chips with broken MUX mode Vojtech Pavlik
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=406682B6.4030505@stesmi.com \
--to=stesmi@stesmi.com \
--cc=aebr@win.tue.nl \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vojtech@suze.cz \
--cc=vojtech@ucw.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