From: "mirabilos" <eccesys@topmail.de>
To: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>,
<root@chaos.analogic.com>
Subject: Re: Linux Post codes during runtime, possibly OT
Date: Tue, 30 Jan 2001 18:41:33 -0000 [thread overview]
Message-ID: <00e401c08aec$caae2820$0100a8c0@homeip.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1010130133314.139A-100000@chaos.analogic.com>
----- Original Message -----
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "mirabilos" <eccesys@topmail.de>
Cc: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>; "Mark H. Wood" <mwood@IUPUI.Edu>
Sent: Tuesday, January 30, 2001 6:36 PM
Subject: Re: Linux Post codes during runtime, possibly OT
> On Tue, 30 Jan 2001, mirabilos wrote:
>
> > [...]
> > > >
> > > > Now, we've found that small delays are reasonably well generated with
> > > > an "outb" to 0x80. So, indeed changing that to something else is going
> > > > to be tricky.
> > >
> > > So how bad would it be to give these people a place to leave the value
> > > that they want to have displayed, and have the delay code write *that*
> > > instead of garbage?
> >
> > Because Port &h80 is _not_ decoded by the standard PC hardware.
> > There are some ISA and nowadays even PCI cards that convert the value
> > OUTted to that port into two 7-segment-digit-LCDisplays, buffered so
> > you can read it from the card, but normally no chipset actually
> > cares about that port. (I speak of Desktop PCs.)
> >
> > I repeat: Any OUT to port &h80 is, as long as there are no special
> > extensions, just as well as any OUT to port &h1234 or &h4711 or
> > whateveryouwant as long as nothing uses it.
> > Since Port &h80 is now "reserved" for that POST code usage,
> > and it is the safest port one can use in order to delay,
> > Linux uses it.
>
> This is not correct. Port 0x80 is not an "unused" port. It
> is decoded by standard hardware:
>
> C:\>debug
>
> -i 80
> AE
> -o 80 20
> -i 80
> 20
> -q
> \x1a
>
> In this machine I do not have a 'POST-codes' board. Port 0x80 is
> an 8-bit read/write latch. It always has been.
>
>
> Cheers,
> Dick Johnson
OK, I'll check it against every box I've got here. I just was
citing what I've learned "ages" ago.
-
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-30 18:45 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
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 [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-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='00e401c08aec$caae2820$0100a8c0@homeip.net' \
--to=eccesys@topmail.de \
--cc=linux-kernel@vger.kernel.org \
--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