From: Gerald Champagne <gerald.champagne@esstech.com>
To: linux-kernel@vger.kernel.org
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: Fri, 15 Mar 2002 11:39:44 -0600 [thread overview]
Message-ID: <3C9231E0.8090202@esstech.com> (raw)
> If we put every single requested obscure fix for one or two boxes into
> the kernel configuration you'd be spending weeks wading through
>
> "Handle weird APM on Dave's homebrew mediagx"
>
> and other questions.
>
A config option that lets you pick the address for the dummy io would
be a pretty obscure option. But having a CONFIG_POST_SUPPORT buried
somewhere wouldn't be that obscure or confusing. If that config
option is set, then a second question would prompt for an alternate
address to be used for the delay io, and a macro would be defined to
display post codes. If the option is unset, then 0x80 would be the
default for the delay address, and the post code macro would be defined
to do nothing.
Gerald
next reply other threads:[~2002-03-15 17:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 17:39 Gerald Champagne [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 15:07 IO delay, port 0x80, and BIOS POST codes Thunder from the hill
[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 ` Andi Kleen
2002-03-15 12:47 ` Martin Wilck
2002-03-15 12:52 ` Andi Kleen
2002-03-14 18:18 Thunder from the hill
2002-03-15 11:46 ` Martin Wilck
2002-03-14 17:11 Martin Wilck
2002-03-14 17:54 ` Richard B. Johnson
2002-03-14 18:10 ` Alan Cox
2002-03-14 19:23 ` Linus Torvalds
2002-03-14 19:46 ` H. Peter Anvin
2002-03-14 20:43 ` John Heil
2002-03-14 21:03 ` Richard B. Johnson
2002-03-14 21:19 ` Pedro M. Rodrigues
2002-03-14 21:26 ` John Heil
2002-03-14 21:41 ` Richard B. Johnson
2002-03-14 21:26 ` Linus Torvalds
2002-03-14 21:44 ` Richard B. Johnson
2002-03-14 21:56 ` H. Peter Anvin
2002-03-14 22:11 ` Richard B. Johnson
2002-03-14 22:20 ` H. Peter Anvin
2002-03-14 22:25 ` Richard B. Johnson
2002-03-14 22:58 ` Alan Cox
2002-03-14 22:56 ` Alan Cox
2002-03-14 21:11 ` H. Peter Anvin
2002-03-14 21:24 ` Linus Torvalds
2002-03-14 21:57 ` H. Peter Anvin
2002-03-14 22:06 ` John Heil
2002-03-14 22:55 ` Alan Cox
2002-03-14 22:39 ` John Heil
2002-03-14 23:29 ` Alan Cox
2002-03-15 0:12 ` David Golden
2002-03-15 0:11 ` John Heil
2002-03-19 14:25 ` Pavel Machek
2002-03-15 11:30 ` Eric W. Biederman
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=3C9231E0.8090202@esstech.com \
--to=gerald.champagne@esstech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox