From: "George Spelvin" <linux@horizon.com>
To: mingo@elte.hu, linux-kernel@vger.kernel.org
Cc: linux@horizon.com
Subject: IO_DELAY documentation
Date: Sun, 17 Feb 2008 20:21:03 -0500 [thread overview]
Message-ID: <20080218012103.31563.qmail@science.horizon.com> (raw)
"make oldconfig" doesn't know how to display the per-item help, so
something like this is needed. It was a squeeze to make all the help
text, plus option prompt, fit into 24 lines. If you think that's not
a concern, some of the wording could be improved.
(Added text placed into the public domain; copyright abandoned.)
diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index 864affc..8e2ceb6 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -157,6 +157,24 @@ config IO_DELAY_TYPE_NONE
choice
prompt "IO delay type"
default IO_DELAY_0XED
+ help
+ The original IBM PC required short pauses between consecutive
+ accesses to its peripheral chips. This can be provided four ways:
+
+ * A dummy write to port 0x80 has been used for 15 years, but
+ crashes the AMD64-based HP dv9000z laptop. The safest option.
+ * Port 0xED is also believed safe, and testing is requested.
+ * Udelay is awkward to implement in the kernel due to processor
+ speed variations, but should be extremely safe.
+ * All but the very oldest PCs use emulations of the original
+ peripheral chips built into a "Super I/O" chip, and usually
+ do no need the delay at all. The most efficient option.
+
+ On the majority of machines, all four options should work.
+ If you have a computer on which any of the four options
+ (especially _0XED or _NONE) does not work, please report it,
+ with a detailed description of the motherboard (and "lspci -nn"
+ and "dmidecode" output), to linux-kernel@vger.kernel.org.
config IO_DELAY_0X80
bool "port 0x80 based port-IO delay [recommended]"
next reply other threads:[~2008-02-18 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 1:21 George Spelvin [this message]
2008-02-18 1:53 ` Calvin Walton
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=20080218012103.31563.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®