From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can we kill f inb_p, outb_p and other random I/O on port 0x80, in 2.6?
Date: Mon, 22 Sep 2003 17:33:12 +0100 [thread overview]
Message-ID: <1064248391.8895.6.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20030922162602.GB27209@mail.jlokier.co.uk>
On Llu, 2003-09-22 at 17:26, Jamie Lokier wrote:
> What sort of timer chip problems do you see? Is it something that can
> be auto-detected, so that timer chip accesses can be made faster on
> boards where that is fine?
CS5520 is one example. Also VIA VP2 seems to care but only very very
occasionally. On my 386 board its reliably borked without the delays
(not sure what chipset and its ISA so harder to tell)
> I've also seen much DOS code that didn't have extra delays for
> keyboard I/Os. What sort of breakage did you observe with the
> keyboard?
DEC laptops hang is the well known example of that one.
I'm *for* making this change to udelay, it just has to start up with a
suitably pessimal udelay assumption until calibrated.
next prev parent reply other threads:[~2003-09-22 16:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 0:27 Eric W. Biederman
2003-09-22 11:22 ` Alan Cox
2003-09-22 16:26 ` Jamie Lokier
2003-09-22 16:33 ` Alan Cox [this message]
2003-09-22 17:11 ` Arjan van de Ven
2003-09-22 18:28 ` Jamie Lokier
2003-09-22 19:09 ` Eric W. Biederman
2003-09-22 19:27 ` Arjan van de Ven
2003-09-22 21:46 ` Jamie Lokier
2003-09-23 18:17 ` bill davidsen
2003-09-22 18:58 ` Eric W. Biederman
2003-09-22 19:19 ` Jamie Lokier
2003-09-23 0:09 ` Alan Cox
2003-09-23 18:20 ` bill davidsen
2003-09-22 19:00 ` Jamie Lokier
2003-09-22 20:05 ` Eric W. Biederman
2003-09-23 18:31 ` bill davidsen
2003-09-23 0:13 ` Alan Cox
[not found] <20030922153651.16497.qmail@science.horizon.com>
2003-09-22 18:35 ` Eric W. Biederman
2003-09-22 21:54 ` Jamie Lokier
2003-09-23 18:41 ` bill davidsen
2003-09-24 17:43 ` Linus Torvalds
2003-09-22 20:03 John Bradford
2003-09-22 21:37 ` Jamie Lokier
2003-09-22 21:42 ` Arjan van de Ven
2003-09-23 0:16 ` Alan Cox
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=1064248391.8895.6.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®