From: Pavel Machek <pavel@suse.cz>
To: Brian Gerst <bgerst@didntduck.org>, root@chaos.analogic.com
Cc: Manfred Spraul <manfred@colorfullife.com>,
rjohnson@analogic.com, linux-kernel@vger.kernel.org
Subject: Re: Linux Post codes during runtime, possibly OT
Date: Sat, 27 Jan 2001 13:28:47 +0100 [thread overview]
Message-ID: <20010127132847.A485@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.3.95.1010126110426.1321B-100000@chaos.analogic.com> <3A71A6DB.B7921B62@didntduck.org>
In-Reply-To: <3A71A6DB.B7921B62@didntduck.org>; from Brian Gerst on Fri, Jan 26, 2001 at 11:33:31AM -0500
Hi!
> > > > + *
> > > > + * Changed the slow-down I/O port from 0x80 to 0x19. 0x19 is a
> > > > + * DMA controller scratch register. rjohnson@analogic.com
> > > > */
> > > >
> > > What about making that a config option?
> > >
> > > default: delay with 'outb 0x80', other options could be
> > > udelay(n); (n=1,2,3)
> > > outb 0x19
> > >
> > > 0x80 is a safe port, and IMHO changing the port on all i386 systems
> > > because it's needed for some embedded system debuggers is too dangerous.
> > >
> > Dangerous? udelay(1) on a 33 MHz system is like udelay(100). Don't
> > get too used to 800+ MHz CPUs. There are systems, probably most in
> > the world, that need 300 +/- nanosecond delays. This is what the
> > port I/O does.
>
> In most of the cases where this delay is needed, it is a _minimum_
> delay. It is usually time enough for the hardware to react to an index
> register being written to, etc. In most cases, a longer delay on slower
> machines should not hurt.
Except getting your ne2000 slower by factor of 300.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-27 17:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 15:42 Linux Post codes during runtime, possibly OT Manfred Spraul
2001-01-26 16:07 ` Richard B. Johnson
2001-01-26 16:33 ` Brian Gerst
2001-01-27 12:28 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 15:41 Petr Vandrovec
2001-01-26 15:07 ` Richard B. Johnson
2001-01-26 15:15 ` Mark Hahn
2001-01-26 15:31 ` Jamie Lokier
2001-01-26 16:03 ` Richard B. Johnson
2001-01-26 16:22 ` Jamie Lokier
2001-01-25 21:46 Ian S. Nelson
2001-01-25 22:26 ` H. Peter Anvin
2001-01-25 22:31 ` Matthew Dharm
2001-01-25 22:32 ` H. Peter Anvin
2001-01-25 22:41 ` Matthew Dharm
2001-01-25 22:45 ` H. Peter Anvin
2001-01-25 23:08 ` Richard B. Johnson
2001-01-25 23:10 ` H. Peter Anvin
2001-01-26 13:58 ` Richard B. Johnson
2001-01-26 16:19 ` H. Peter Anvin
2001-01-26 17:54 ` David Welch
2001-01-29 2:35 ` Paul Gortmaker
2001-01-27 10:20 ` Rogier Wolff
2001-01-27 20:47 ` H. Peter Anvin
2001-01-27 21:01 ` Rogier Wolff
2001-01-27 21:24 ` H. Peter Anvin
2001-01-28 10:12 ` Rogier Wolff
2001-01-28 10:18 ` H. Peter Anvin
2001-01-28 11:03 ` Rogier Wolff
2001-01-28 17:22 ` Jamie Lokier
2001-01-28 22:34 ` Pavel Machek
2001-01-29 15:09 ` Richard B. Johnson
2001-01-29 19:21 ` H. Peter Anvin
2001-01-28 22:29 ` Pavel Machek
2001-01-30 17:44 ` Mark H. Wood
2001-01-30 18:10 ` Richard B. Johnson
2001-01-30 18:16 ` mirabilos
2001-01-30 18:36 ` Richard B. Johnson
2001-01-30 18:41 ` mirabilos
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=20010127132847.A485@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rjohnson@analogic.com \
--cc=root@chaos.analogic.com \
/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.