From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Dave Jones <davej@codemonkey.org.uk>, Jens Axboe <axboe@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PS2 mouse going nuts during cdparanoia session.
Date: 17 Jul 2003 12:15:04 +0100 [thread overview]
Message-ID: <1058440490.8620.18.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030716234711.GA22010@ucw.cz>
Dave just a random pondering looking over the code - does it make any
difference if you stick a udelay(50) at the top of wait_read and
wait_write in i8042.c. Right now we don't always seem to honour the
delays for certain specific patterns of I/O and interrupt.
Ditto the read_status/read_data loop in the _interrupt code path.
next prev parent reply other threads:[~2003-07-17 11:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 16:57 PS2 mouse going nuts during cdparanoia session Dave Jones
2003-07-16 17:03 ` Jens Axboe
2003-07-16 17:09 ` Dave Jones
2003-07-16 17:13 ` Jens Axboe
2003-07-16 17:20 ` Dave Jones
2003-07-16 17:24 ` Jens Axboe
2003-07-16 17:21 ` Markus Plail
2003-07-16 17:10 ` Alan Cox
2003-07-16 17:16 ` Jens Axboe
2003-07-16 17:23 ` Dave Jones
2003-07-16 17:25 ` Jens Axboe
2003-07-16 17:28 ` Dave Jones
2003-07-16 17:31 ` Jens Axboe
2003-07-16 18:22 ` Alan Cox
2003-07-16 19:03 ` Kristofer T. Karas
2003-07-16 19:13 ` Valdis.Kletnieks
2003-07-16 19:00 ` Vojtech Pavlik
2003-07-16 19:30 ` Dave Jones
2003-07-16 20:53 ` Vojtech Pavlik
2003-07-16 23:31 ` Dave Jones
2003-07-16 23:47 ` Vojtech Pavlik
2003-07-17 11:15 ` Alan Cox [this message]
2003-07-17 17:08 ` Dave Jones
2003-07-16 18:00 ` Andrew Morton
2003-07-16 18:56 ` Vojtech Pavlik
2003-07-16 21:05 ` Andries Brouwer
2003-07-16 17:10 ` Valdis.Kletnieks
2003-07-16 17:17 ` Jens Axboe
2003-07-16 17:55 ` Dave Jones
2003-07-16 17:57 ` Jens Axboe
[not found] ` <1058422511.1164.1440.camel@workshop.saharacpt.lan>
2003-07-17 12:39 ` Dave Jones
2003-07-16 23:43 Mikael Pettersson
2003-07-17 2:03 ` Jacek Kawa
2003-07-17 21:44 ` Jacek Kawa
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=1058440490.8620.18.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=davej@codemonkey.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).