public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "H. Peter Anvin" <hpa@transmeta.com>,
	Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Post codes during runtime, possibly OT
Date: Sun, 28 Jan 2001 23:34:25 +0100	[thread overview]
Message-ID: <20010128233425.E1300@bug.ucw.cz> (raw)
In-Reply-To: <200101281012.LAA04278@cave.bitwizard.nl> <3A73F1EB.B6F69A93@transmeta.com>
In-Reply-To: <3A73F1EB.B6F69A93@transmeta.com>; from H. Peter Anvin on Sun, Jan 28, 2001 at 02:18:19AM -0800

Hi!

> > Ok. I've thought about it some more, but I don't care enough about
> > this issue to do the painstaking legwork: I don't have one of those
> > POST-code indicators on port 0x80.
> > 
> > I've made the "pause" in outb_p just a few (*) ns slower, because it
> > now loads a variable before outputting the value to port 0x80. As the
> > whole idea about this is "pausing", making it a bit slower shouldn't
> > matter too much.  I've tested it: It compiles, it boots.
> > 
> > I'm not too familar with the syntax of the "asm" statement. So I may
> > illegally be modifying the AX register. I don't care enough about this
> > to figure it out right now.
> > 
> 
> It is; you'd have to specify "eax" as a clobber value, and that is
> undesirable.
> 
> And you're still overwriting the POST value written by the BIOS.

So save value from bios at initial boot ;-).
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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/

  parent reply	other threads:[~2001-01-29 14:41 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 [this message]
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=20010128233425.E1300@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=hpa@transmeta.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