summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Reinauer <reinauer@chromium.org>2012-11-12 15:17:24 -0800
committerRonald G. Minnich <rminnich@gmail.com>2012-11-13 07:09:09 +0100
commit455f4b432835828e82531adf967b9c7d8fc812dc (patch)
tree30fdf2f593ce3325b5a386afa1126c2898afc9e0
parent000bf83c934880490d6b1b4c16465cbe7f4f377c (diff)
downloadcoreboot-455f4b432835828e82531adf967b9c7d8fc812dc.tar.xz
Fix CONFIG_MAX_CPU set to 1 CPU build problem
There are some function dependancies that didn't work when MAX_CPU was set to 1 and the build would fail. Change-Id: I033a42056f7b48a40316e03772ed89ad9cb013fe Signed-off-by: Marc Jones <marc.jones@se-eng.com> Reviewed-on: http://review.coreboot.org/1819 Reviewed-by: Ronald G. Minnich <rminnich@gmail.com> Tested-by: build bot (Jenkins)
-rw-r--r--src/cpu/intel/model_206ax/model_206ax_init.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/cpu/intel/model_206ax/model_206ax_init.c b/src/cpu/intel/model_206ax/model_206ax_init.c
index f34c589852..64c32a0bc9 100644
--- a/src/cpu/intel/model_206ax/model_206ax_init.c
+++ b/src/cpu/intel/model_206ax/model_206ax_init.c
@@ -513,12 +513,14 @@ static void intel_cores_init(device_t cpu)
cpu->path.apic.apic_id,
new->path.apic.apic_id);
+#if CONFIG_SMP && CONFIG_MAX_CPUS > 1
/* Start the new cpu */
if (!start_cpu(new)) {
/* Record the error in cpu? */
printk(BIOS_ERR, "CPU %u would not start!\n",
new->path.apic.apic_id);
}
+#endif
}
}