Re: Linux Post codes during runtime, possibly OT

[Mark H. Wood]

On Sat, 27 Jan 2001, Rogier Wolff wrote:
[snip]
> I may have missed too much of the discussion, but I thought that the
> idea was that some people noted that their POST-code-cards don't
> really work all that well when Linux is running because Linux keeps on
> sending garbage to port 0x80. 
> 
> You seem to state that if you want POST codes, you should find a
> different port, modify the code, test the hell out of it, and then
> submit the patch.
> 
> That is NOT the right way to go about this: Port 0x80 is RESERVED for
> POST usage, that's why it's always free. If people want to use it for
> the original purpose then that is a pretty damn good reason to bump
> the non-intended users of that port somewhere else. 
> 
> 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?

-- 
Mark H. Wood, Lead System Programmer   [e-mail]
Make a good day.