diff options
| author | Amar Takhar <amar@rtems.org> | 2016-01-18 00:37:40 -0500 |
|---|---|---|
| committer | Amar Takhar <verm@darkbeer.org> | 2016-05-02 20:51:24 -0400 |
| commit | d389819eea3a84e388935153e3be847342809da3 (patch) | |
| tree | 15cfe55f41281cead805ce87f66c5d7248caa9ce /porting/interrupts.rst | |
| parent | Remove ada_user document. (diff) | |
| download | rtems-docs-d389819eea3a84e388935153e3be847342809da3.tar.bz2 | |
Convert all Unicode to ASCII(128)
Diffstat (limited to 'porting/interrupts.rst')
| -rw-r--r-- | porting/interrupts.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/porting/interrupts.rst b/porting/interrupts.rst index d6958ab..8a69e1a 100644 --- a/porting/interrupts.rst +++ b/porting/interrupts.rst @@ -305,7 +305,7 @@ The ``_ISR_Handler`` routine provides the RTEMS interrupt management. This discussion ignores a lot of the ugly details in a real implementation such as saving enough registers/state to be able to do something real. -Keep in mind that the goal is to invoke a user’s ISR handler which is +Keep in mind that the goal is to invoke a user's ISR handler which is written in C. That ISR handler uses a known set of registers thus allowing the ISR to preserve only those that would normally be corrupted by a subroutine call. @@ -368,7 +368,7 @@ specific wrapper for ``_Thread_Dispatch`` used in this case. ISR Invoked with Frame Pointer ------------------------------ -Does the RTEMS invoke the user’s ISR with the vector number and a pointer +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)? .. code:: c |