From: Vojtech Pavlik <vojtech@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Pozsar Balazs <pozsy@sch.bme.hu>, Dave Jones <davej@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.2-dj7
Date: Wed, 30 Jan 2002 19:31:36 +0100 [thread overview]
Message-ID: <20020130193136.B2487@suse.cz> (raw)
In-Reply-To: <E16Vie4-0005gE-00@the-village.bc.nu> <Pine.LNX.4.10.10201301018200.7609-100000@www.transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10201301018200.7609-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Wed, Jan 30, 2002 at 10:22:02AM -0800
On Wed, Jan 30, 2002 at 10:22:02AM -0800, James Simmons wrote:
> > > In dmi_scan.c there is a hook to deal with the PS/2 mouse on Dell
> > > Latitude C600. Can someone with this machine test the new input drivers on
> > > it. I like to see if we need some kind of fix for this device.
> >
> > You I suspect will. When the machine resumes it likes to re-enable the mouse
> > pad irrespective of whether it is being used - so you get an IRQ12. Even
> > more fun if you ignore that IRQ you dont get keyboard events because the
> > microcontroller (or SMM code impersonating it - who knows these days) is
> > waiting for the ps/2 event to be handled first.
>
> Oh man is that brain dead.
The i8042 has a single byte output buffer shared by both the keyboard
and a mouse. If it's full, no more data is accepted from the keyboard or
mouse. Hence the problem above.
> > The alternative (possibly cleaner) fix on those machines would be to turn
> > the PS/2 port on always and process/discard output if its not wanted by
> > the user
>
> This could be easily arranged with the new input drivers with it modular
> design. Since for the ix86 platform most people will want PS/2 input
> support to be built in. The only expection are the USB only users. I guess
> with the Dell Latitude C600 we will have to force i8042.c to be built in.
> Vojtech what do you think about this solution?
I don't think we need to have it built in. If we need keyboard support
(which is likely), we'll have it, and if we don't need keyboard, then
we can safely ignore the IRQ12 as well.
And i8042.c, once power management is implemented in it, will reset the
keyboard controller and flush its buffers upon resume from sleep anyway.
(A problem may arise if the machine doesn't tell us about sleep/wake and
handles it all in SMM ...)
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-01-30 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 22:55 Linux 2.5.2-dj7 Dave Jones
2002-01-29 23:19 ` Pozsar Balazs
2002-01-29 23:33 ` Dave Jones
2002-01-29 23:52 ` Pozsar Balazs
2002-01-30 0:05 ` James Simmons
2002-01-30 0:20 ` Pozsar Balazs
2002-01-30 0:30 ` Alan Cox
2002-01-30 18:22 ` James Simmons
2002-01-30 18:31 ` Vojtech Pavlik [this message]
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=20020130193136.B2487@suse.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/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