From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cleanup port 0x80 use (was: Re: IO delay ...)
Date: Fri, 15 Mar 2002 21:33:45 +0000 (UTC) [thread overview]
Message-ID: <a6tpbp$snd$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203151736460.1477-100000@biker.pdb.fsc.net> <E16lw5V-0004ES-00@the-village.bc.nu> <a6tm95$c55$1@cesium.transmeta.com>
In article <a6tm95$c55$1@cesium.transmeta.com>,
H. Peter Anvin <hpa@zytor.com> wrote:
>
>The ISA bus doesn't time out; a cycle on the ISA bus just happens, and
>the fact that noone is there to listen doesn't seem to matter.
The ISA bus doesn't time out, but the PCI access before it gets
forwarded to the ISA bus _does_, if the ISA bus is decoded using
nagative decoding.
This is why it's important that there not be a motherboard PCI device
that can decode the port - because if there is, the access is
potentially a much faster PCI-only decode.
Note that this really only matters on low-end machines anyway, as the
whole "inb_p()" thing tends to be used only for old ISA devices. If you
have a new machine that is all PCI, I doubt that port 80h access matters
not at all.
(Another way of saying it: if you have a machine with a PCI POST card,
none of this will matter)
Linus
next prev parent reply other threads:[~2002-03-15 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C90E983.5AC769B8@ngforever.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0203151243430.1477-100000@biker.pdb.fsc.net.suse.lists.linux.kernel>
2002-03-15 11:51 ` IO delay, port 0x80, and BIOS POST codes Andi Kleen
2002-03-15 12:47 ` Martin Wilck
2002-03-15 12:52 ` Andi Kleen
2002-03-15 17:41 ` [PATCH] Cleanup port 0x80 use (was: Re: IO delay ...) Martin Wilck
2002-03-15 18:05 ` Alan Cox
2002-03-15 20:41 ` H. Peter Anvin
2002-03-15 21:33 ` Linus Torvalds [this message]
2002-03-15 21:37 ` Alan Cox
2002-03-16 0:01 ` H. Peter Anvin
2002-03-15 18:57 ` Andreas Dilger
2002-03-15 20:17 ` Martin Wilck
2002-03-17 2:01 ` Jamie Lokier
2002-03-18 9:18 ` Martin Wilck
2002-03-18 9:39 ` Keith Owens
2002-03-18 11:20 ` Martin Wilck
2002-03-18 15:22 ` Jamie Lokier
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='a6tpbp$snd$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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.