Changeset 797c232 in rtems
- Timestamp:
- 01/22/08 15:20:34 (16 years ago)
- Branches:
- 4.10, 4.11, 4.9, 5, master
- Children:
- 14862663
- Parents:
- b4df56dd
- Location:
- cpukit
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
cpukit/ChangeLog
rb4df56dd r797c232 1 2008-01-22 Joel Sherrill <joel.sherrill@OARcorp.com> 2 3 * libi2c/README_libi2c: Correct spelling error. 4 * score/src/threadclearstate.c: Improve comment. 5 1 6 2008-01-18 Jennifer Averett <jennifer.averett@OARcorp.com> 2 7 -
cpukit/libi2c/README_libi2c
rb4df56dd r797c232 41 41 layering is: 42 42 43 +--------------------------------------- +44 6| Application |45 +--------------------------------------- +46 5| RTEMS I/O Manager |47 +--------------------------------------- +48 4|** libi2c OS adaption layer **|49 +--------------------------------------- +50 3| high level i2c device driver |51 | (EEPROM, RTC, ...) |52 | (e.g. in c/src/libchip/i2c) |53 +--------------------------------------- +54 2|** libi2c low level abstra tion layer **|55 +--------------------------------------- +56 1| i2c controller driver |57 | (in BSP) |58 +--------------------------------------- +43 +----------------------------------------+ 44 6| Application | 45 +----------------------------------------+ 46 5| RTEMS I/O Manager | 47 +----------------------------------------+ 48 4|** libi2c OS adaption layer **| 49 +----------------------------------------+ 50 3| high level i2c device driver | 51 | (EEPROM, RTC, ...) | 52 | (e.g. in c/src/libchip/i2c) | 53 +----------------------------------------+ 54 2|** libi2c low level abstraction layer **| 55 +----------------------------------------+ 56 1| i2c controller driver | 57 | (in BSP) | 58 +----------------------------------------+ 59 59 60 60 This document will describe the following interfaces in separate -
cpukit/score/src/threadclearstate.c
rb4df56dd r797c232 76 76 /* 77 77 * If the thread that was unblocked is more important than the heir, 78 * then we have a new heir. In addition, if the current thread 79 * is preemptible or we are waking up one of the "pseudo-ISR" system 80 * threads, then we need to do a context switch. 78 * then we have a new heir. This may or may not result in a 79 * context switch. 80 * 81 * Normal case: 82 * If the current thread is preemptible, then we need to do 83 * a context switch. 84 * Pseudo-ISR case: 85 * Even if the thread isn't preemptible, if the new heir is 86 * a pseudo-ISR system task, we need to do a context switch. 81 87 */ 82 88 if ( the_thread->current_priority < _Thread_Heir->current_priority ) {
Note: See TracChangeset
for help on using the changeset viewer.