[coreboot] [PATCH] Halt TCO timer on Intel 3100 chipset

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Wed Apr 16 18:44:03 CEST 2008

On 16.04.2008 18:36, Jeremy Jackson wrote:
> On Wed, 2008-04-16 at 18:12 +0200, Carl-Daniel Hailfinger wrote:
>>> On Wed, 2008-04-16 at 17:33 +0200, Carl-Daniel Hailfinger wrote:
>>>> Please avoid any POST code toggling. There are POST boards out there
>>>> which display the last n POST codes and make it a lot easier to follow
>>>> the code path. Once you add POST code toggling, that history is flushed
>>>> away really fast.
>> We have some places where we output POST codes in a tight loop in a
>> die() function (or whatever it is called). Coupling watchdog timer reset
>> with outputting POST codes makes sure that the machine will NEVER reboot
>> on serious errors and we might as well disable the watchdog altogether.
> How does this outputing in a loop interact with the above mentioned POST
> cards that store a history?
> What is the purpose of these outputs in die() loops?

Ron had the problem that accessing a CPU with a FS2 was difficult if no
I/O operations were done. So we now die with continuous output.


More information about the coreboot mailing list