summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRandall Spangler <rspangler@chromium.org>2012-08-31 11:13:41 -0700
committerGerrit <chrome-bot@google.com>2012-08-31 15:41:35 -0700
commit66d3ad01709e58cd0299147aa6b59d634322a018 (patch)
tree12b4cdb08b3833bfba8913595d1ff14124cb9904 /README
parentf3de461a35b4668f16e6a75ef1211208615155a3 (diff)
downloadchrome-ec-66d3ad01709e58cd0299147aa6b59d634322a018.tar.gz
Use new panic stack on all platforms
Now that the panic stack goes at the end of RAM, there's no overhead to using it on all platforms. When it was a dedicated block of memory, we needed to turn it off on some low-RAM platforms (e.g. Snow). BUG=chrome-os-partner:7466 TEST='crash divzero' or 'crash unaligned'; should print dump and reboot BRANCH=all Change-Id: Iddfeb134e237538215df51abe4e16ee831b3ae2d Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/32037 Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r--README6
1 files changed, 0 insertions, 6 deletions
diff --git a/README b/README
index 3a122e1894..700adcc624 100644
--- a/README
+++ b/README
@@ -34,12 +34,6 @@ Build Options
This is needed on STM32, where the independent watchdog has no early
warning feature and the windowed watchdog has a very short period.
-- CONFIG_PANIC_NEW_STACK
-
- When reporting a panic, change to a completely new stack. This might
- help get a useful trace out a situation where the stack or stack
- pointer has been corrupted.
-
- CONFIG_PANIC_HELP
Report extra information about a panic, such as the fault address,