Changeset d389819 in rtems-docs for porting/interrupts.rst


Ignore:
Timestamp:
Jan 18, 2016, 5:37:40 AM (5 years ago)
Author:
Amar Takhar <amar@…>
Branches:
4.11, 5, master
Children:
f916fca
Parents:
11e1a6f
git-author:
Amar Takhar <amar@…> (01/18/16 05:37:40)
git-committer:
Amar Takhar <verm@…> (05/03/16 00:51:24)
Message:

Convert all Unicode to ASCII(128)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • porting/interrupts.rst

    r11e1a6f rd389819  
    306306This discussion ignores a lot of the ugly details in a real implementation
    307307such as saving enough registers/state to be able to do something real.
    308 Keep in mind that the goal is to invoke a user’s ISR handler which is
     308Keep in mind that the goal is to invoke a user's ISR handler which is
    309309written in C.  That ISR handler uses a known set of registers thus
    310310allowing the ISR to preserve only those that would normally be corrupted
     
    369369------------------------------
    370370
    371 Does the RTEMS invoke the user’s ISR with the vector number and a pointer
     371Does the RTEMS invoke the user's ISR with the vector number and a pointer
    372372to the saved interrupt frame (1) or just the vector number (0)?
    373373.. code:: c
Note: See TracChangeset for help on using the changeset viewer.