summaryrefslogtreecommitdiffstats
path: root/doc/porting/interrupts.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>2000-07-03 20:05:17 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>2000-07-03 20:05:17 +0000
commitc2f39fff1f489c8c2063ddae3e230cc711e525c4 (patch)
tree97670065fc17b118bfa4d6cbf223657636190e80 /doc/porting/interrupts.t
parentInterrupt stack is allocated in _ISR_Handler_initialization not (diff)
downloadrtems-c2f39fff1f489c8c2063ddae3e230cc711e525c4.tar.bz2
Interrupt stack is allocated by _ISR_Handler_initialization
not that of _ISR_Manager_initialization.
Diffstat (limited to 'doc/porting/interrupts.t')
-rw-r--r--doc/porting/interrupts.t2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/porting/interrupts.t b/doc/porting/interrupts.t
index a73c21c0d0..a73a16a753 100644
--- a/doc/porting/interrupts.t
+++ b/doc/porting/interrupts.t
@@ -157,7 +157,7 @@ interrupt stack is managed by RTEMS in software or the CPU has direct
support for an interrupt stack. If RTEMS is to manage a dedicated
interrupt stack in software, then this macro should be set to TRUE and the
memory for the software managed interrupt stack is allocated in
-_Interrupt_Manager_initialization. If this macro is set to FALSE, then
+@code{_ISR_Handler_initialization}. If this macro is set to FALSE, then
RTEMS assumes that the hardware managed interrupt stack is supported by
this CPU. If the CPU has a hardware managed interrupt stack, then the
porter has the option of letting the BSP allcoate and initialize the