From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: root@chaos.analogic.com,
Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux Post codes during runtime, possibly OT
Date: Sun, 28 Jan 2001 21:35:47 -0500 [thread overview]
Message-ID: <3A74D703.59578FA8@yahoo.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010126085110.265A-100000@chaos.analogic.com> <3A71A3AE.DE587EEE@transmeta.com>
> Actually, what you need to do is change it and then try it on something
> like 300 different systems. Since noone has direct access to that kind
> of system, you have to get people to help you out trying it.
>
> A better idea might be to find out what port, if any, Windows uses. If
> Windows does it, it is usually safe.
In the FWIW category, the collection of DOS packet drivers from Russ Nelson
(and the many commercial ones based on them) use a read of the NMI status
port to create a similar delay. This code got used on lots of hardware
(although probably not much on current hw - mostly 386/486 type vintage
stuff I'd guess...)
I'm not advocating we move off 0x80 either - but people wanting to use
POST cards have at least a couple of options. And if they have a POST
card, it is probably a safe bet that they can manage to apply one of
the patches and rebuild the kernel.
Paul.
[Booted old 486-66 with 8390 based card (uses inb_p/outb_p) & works fine]
--- include/asm-i386/io.h~ Thu May 11 15:19:27 2000
+++ include/asm-i386/io.h Sun Jan 28 21:10:22 2001
@@ -23,6 +23,11 @@
* I feel a bit unsafe about using 0x80 (should be safe, though)
*
* Linus
+ *
+ * Some people get upset since they can't use their POST cards
+ * for diagnostics once linux boots and hammers 0x80 with garbage.
+ * DOS packet drivers do a dummy read of the NMI status port to
+ * obtain a similar delay. Paul G.
*/
/*
@@ -32,7 +37,11 @@
#ifdef SLOW_IO_BY_JUMPING
#define __SLOW_DOWN_IO "\njmp 1f\n1:\tjmp 1f\n1:"
#else
+#ifdef HAVE_POST_CARD
+#define __SLOW_DOWN_IO "\n\tpushl %%eax\n\tinb $0x61,%%al\n\tpopl %%eax"
+#else
#define __SLOW_DOWN_IO "\noutb %%al,$0x80"
+#endif
#endif
#ifdef REALLY_SLOW_IO
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
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-29 8:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 21:46 Linux Post codes during runtime, possibly OT 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 [this message]
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
-- 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-26 15:42 Manfred Spraul
2001-01-26 16:07 ` Richard B. Johnson
2001-01-26 16:33 ` Brian Gerst
2001-01-27 12:28 ` Pavel Machek
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=3A74D703.59578FA8@yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox