All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: John Heil <kerndev@sc-software.com>,
	<linux-kernel@vger.kernel.org>,
	Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: 15 Mar 2002 04:30:44 -0700	[thread overview]
Message-ID: <m1u1rixe3f.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0203141318130.9855-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0203141318130.9855-100000@penguin.transmeta.com>

Linus Torvalds <torvalds@transmeta.com> writes:

> On Thu, 14 Mar 2002, John Heil wrote:
> > 
> > No, the better/correct port is 0xED which removes the conflict.
> 
> Port ED is fine for a BIOS, which (by definition) knows what the
> motherboard devices are, and thus knows that ED cannot be used by
> anything.
> 
> But it _is_ an unused port, and that's exactly the kind of thing that
> might be used sometime in the future. Remember the port 22/23 brouhaha
> with Cyrix using it for their stuff, and later Intel getting into the fray
> too?
> 
> So the fact that ED works doesn't mean that _stays_ working.
> 
> The fact that 80 is the post code register means that it is fairly likely 
> to _stay_ that way, without any ugly surprises.
> 
> Now, if there is something _else_ than just the fact that it is unused
> that makes ED a good choice in the future too, that might be worth looking
> into (like NT using it for the same purpose as Linux does port 80),

Does the logic outb_p uses continue to work if you have a PCI post
card (possibly on the motherboard).  And an ISA device?

Systems without ISA slots but with ISA or LPC devices onboard must
use a PCI post card so I have trouble believing that outb_b and friends
really work as expected....


Eric

  parent reply	other threads:[~2002-03-15 11:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 17:11 IO delay, port 0x80, and BIOS POST codes 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=m1u1rixe3f.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=Martin.Wilck@fujitsu-siemens.com \
    --cc=kerndev@sc-software.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.