All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: 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: 23 Sep 2003 18:31:41 GMT	[thread overview]
Message-ID: <bkq3id$f0u$1@gatekeeper.tmr.com> (raw)
In-Reply-To: m1wuc0io78.fsf@ebiederm.dsl.xmission.com

In article <m1wuc0io78.fsf@ebiederm.dsl.xmission.com>,
Eric W. Biederman <ebiederm@xmission.com> wrote:
| Jamie Lokier <jamie@shareable.org> writes:

| > Unfortunately, there are a lot of drivers, and a lot of x86
| > arch-specific code, which use the delay operaters.  There's no real
| > way to verify that all the drivers are fine when the delay is reduced
| > or removed.
| 
| We just need something sufficiently good.  If the delay is removed
| on a system that needs it someone will complain.

The only problem with that is that is that (a) a complaint and a dollar
will get you a cheap beer, but this is Linux and no one *needs* to fix
it, therefore not breaking it becomes more important. The top developers
are not running legacy 386's, I bet. And (b) if the problem comes up
months from now, will anyone think to try timing changes for "every once
in a while" problems.

I really like the isa_delay() idea, or similar, which will be in a
single place and probably get enough attention to make it work. It just
sounds like a safer way to go with equal benefits.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2003-09-23 18:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22  0:27 Can we kill f inb_p, outb_p and other random I/O on port 0x80, in 2.6? Eric W. Biederman
2003-09-22 11:22 ` Alan Cox
2003-09-22 16:26   ` Jamie Lokier
2003-09-22 16:33     ` Alan Cox
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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='bkq3id$f0u$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --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 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.