summaryrefslogtreecommitdiff
path: root/src/superio
diff options
context:
space:
mode:
authorScott Duplichan <scott@notabs.org>2010-10-19 04:26:17 +0000
committerScott Duplichan <scott@notabs.org>2010-10-19 04:26:17 +0000
commitaf786b618d5e1aafe1e5b8d9ed49b55903381a2e (patch)
tree9151e98cdbd799b282888d5585fd97cc6ca63f5c /src/superio
parentd7acdfb44acfcebe6107b7286c5e4b79f25a33e0 (diff)
When debug logging is enabled, a message such as '* AP 02 timed out:02010501'
is sometimes logged. The reason is that the AP first sets a completion value such as 0x13, which is what function wait_cpu_state() is waiting for. Then a short time later, the AP calls function init_fidvid_ap(). This function sets a completion value of 01. When logging is off, wait_cpu_state is fast enough to see the initial completion value for each of the APs. But with logging enabled, one or more APs may go on to complete function init_fidvid_ap, which sets the completion value to 01. While mostly harmless, the timeout does increase boot time. This patch eliminates the timeout by making function wait_cpu_state recognize 01 as an additional valid AP completion value. Signed-off-by: Scott Duplichan <scott@notabs.org> Acked-by: Peter Stuge <peter@stuge.se> git-svn-id: svn://svn.coreboot.org/coreboot/trunk@5966 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'src/superio')
0 files changed, 0 insertions, 0 deletions