summaryrefslogtreecommitdiffstats
path: root/c/src/exec/score/cpu/sh
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-06-03 19:00:17 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-06-03 19:00:17 +0000
commit937a6f3cefda65300a82e25fd024607881eae53c (patch)
treeec5e63c45b8e85b7b60362b5adef2d3e251eff71 /c/src/exec/score/cpu/sh
parentCorrected macros for assembly language program sections. (diff)
downloadrtems-937a6f3cefda65300a82e25fd024607881eae53c.tar.bz2
Added CPU_ISR_PASSES_FRAME_POINTER so some ports could pass just the
vector number to user ISR's and other ports could pass both the vector number and a pointer to the ISF.
Diffstat (limited to 'c/src/exec/score/cpu/sh')
-rw-r--r--c/src/exec/score/cpu/sh/cpu.h7
1 files changed, 7 insertions, 0 deletions
diff --git a/c/src/exec/score/cpu/sh/cpu.h b/c/src/exec/score/cpu/sh/cpu.h
index 310e3271f6..9ff5319aa3 100644
--- a/c/src/exec/score/cpu/sh/cpu.h
+++ b/c/src/exec/score/cpu/sh/cpu.h
@@ -108,6 +108,13 @@ extern "C" {
*/
#define CPU_ALLOCATE_INTERRUPT_STACK FALSE
+/*
+ * Does the RTEMS invoke the user's ISR with the vector number and
+ * a pointer to the saved interrupt frame (1) or just the vector
+ * number (0)?
+ */
+
+#define CPU_ISR_PASSES_FRAME_POINTER 0
/*
* Does the CPU have hardware floating point?