mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Heil <kerndev@sc-software.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>,
	Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: Thu, 14 Mar 2002 12:43:44 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0203141234170.1286-100000@scsoftware.sc-software.com> (raw)
In-Reply-To: <a6qtb8$6fg$1@penguin.transmeta.com>

On Thu, 14 Mar 2002, Linus Torvalds wrote:

> Date: Thu, 14 Mar 2002 19:23:20 +0000 (UTC)
> From: Linus Torvalds <torvalds@transmeta.com>
> To: linux-kernel@vger.kernel.org
> Subject: Re: IO delay, port 0x80, and BIOS POST codes
>
> In article <E16lZg3-0001Ug-00@the-village.bc.nu>,
> Alan Cox  <alan@lxorguk.ukuu.org.uk> wrote:
> >> Unfortunately we can't read this information because Linux uses
> >> port 80 as "dummy" port for delay operations. (outb_p and friends,
> >> actually there seem to be a more hard-coded references to port
> >> 0x80 in the code).
> >
> >The dummy port needs to exist. By using 0x80 we have probably the only
> >port we can safely use in this way. We know it fouls old style POST
> >boards on odd occasions.
>
> In fact, port 0x80 is safe exactly _because_ it is used for BIOS POST
> codes, which pretty much guarantees that it will never be used for
> anything else. That tends to not be as true of any other ports.
>
> Also, it should be noted that to get the 1us delay, the port should be
> behind the ISA bridge in a legacy world (in a modern all-PCI system it
> doesn't really matter, because the ports that need more delays are
> faster too, so this works out ok).  That's why I personally would be
> nervous about using some of the well-specified (but irrelevant) ports
> that are on the PCI side of a super-IO controller.
>
> I suspect the _real_ solution is to stop using "inb_p/outb_p" and make
> the delay explicit, although it may be that some drivers depend on the
> fact that not only is the "outb $0x80" a delay, it also tends to act as
> a posting barrier.
>
> 			Linus

No, the better/correct port is 0xED which removes the conflict.

We've used 0xED w/o problem doing an embedded linux implementation
at kernel 2.4.1, where SMM issues were involved. (It was recommended
to me by an x-Phoenix BIOS developer, because of its safety as well as
conflict resolution,

Johnh

-
-----------------------------------------------------------------
John Heil
South Coast Software
Custom systems software for UNIX and IBM MVS mainframes
1-714-774-6952
johnhscs@sc-software.com
http://www.sc-software.com
-----------------------------------------------------------------


  parent reply	other threads:[~2002-03-14 20:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2002-03-14 18:18 Thunder from the hill
2002-03-15 11:46 ` Martin Wilck
     [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-15 15:07 Thunder from the hill
2002-03-15 17:39 Gerald Champagne

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=Pine.LNX.4.33.0203141234170.1286-100000@scsoftware.sc-software.com \
    --to=kerndev@sc-software.com \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®