| commit | 858f96d28d8d0aeffe58e1d4d1d559ad161aab66 | [log] [tgz] |
|---|---|---|
| author | Aaron Durbin <adurbin@chromium.org> | Tue Sep 17 22:01:48 2013 -0500 |
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | Fri Sep 20 00:52:23 2013 +0000 |
| tree | f9adc77692d4c644a8ca882d3b41d49a0357cb63 | |
| parent | 98c00dc269506547ea178f0fd41e11191b67a413 [diff] |
model_106cx: don't blindly set Kconfig settings The CPU_ADDR_BITS was being unconditionally set. Don't do that. BUG=None BRANCH=None TEST=Built bayleybay and can now set CPU_ADDR_BITS properly. Change-Id: Idbc63328fade8f5f05f7f46282139b86e6694989 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/169711 Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
diff --git a/src/cpu/intel/model_106cx/Kconfig b/src/cpu/intel/model_106cx/Kconfig index e26bf1f..7516106 100644 --- a/src/cpu/intel/model_106cx/Kconfig +++ b/src/cpu/intel/model_106cx/Kconfig
@@ -7,7 +7,10 @@ select AP_IN_SIPI_WAIT select TSC_SYNC_MFENCE +if CPU_INTEL_MODEL_106CX + config CPU_ADDR_BITS int default 32 +endif