Re: Linux Post codes during runtime, possibly OT

[Rogier Wolff]

H. Peter Anvin wrote:
> Rogier Wolff wrote:
> > 
> > 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.

OK. Then someone needs to do the legwork, and add that.

The "_P" version is intended to be inefficient "because the device
can't handle us pushing the limit". Thus a little more because of an
eax reload is unfortunate, but not the end of the world.

Everybody knows (I hope) that outb_p is not intended as an efficient
way to output a byte. So, when possible everybody should be avoiding
it already.

> And you're still overwriting the POST value written by the BIOS.

Yes, but by the time Linux boots, we should just start putting OUR
values there. If the BIOS goes up to 0x8f, then Linux could start at
0x90 and continue there. I don't have one of those thingies, so I
don't know what the last value would be that the BIOS leaves there.

				Roger. 

-- 
** [e-mail] ** http://www.BitWizard.nl/ ** [phone] **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots.