2008-01-22 Joel Sherrill <joel.sherrill@OARcorp.com>

* libi2c/README_libi2c: Correct spelling error.
	* score/src/threadclearstate.c: Improve comment.
This commit is contained in:
Joel Sherrill
2008-01-22 15:20:34 +00:00
parent b4df56ddb4
commit 797c232dad
3 changed files with 30 additions and 19 deletions
+5
View File
@@ -1,3 +1,8 @@
2008-01-22 Joel Sherrill <joel.sherrill@OARcorp.com>
* libi2c/README_libi2c: Correct spelling error.
* score/src/threadclearstate.c: Improve comment.
2008-01-18 Jennifer Averett <jennifer.averett@OARcorp.com>
* posix/include/rtems/posix/timer.h, posix/src/cleanuppop.c,
+16 -16
View File
@@ -40,22 +40,22 @@ Structure
This library defines a layered API to i2c and spi devices. The
layering is:
+---------------------------------------+
6| Application |
+---------------------------------------+
5| RTEMS I/O Manager |
+---------------------------------------+
4|** libi2c OS adaption layer **|
+---------------------------------------+
3| high level i2c device driver |
| (EEPROM, RTC, ...) |
| (e.g. in c/src/libchip/i2c) |
+---------------------------------------+
2|** libi2c low level abstration layer **|
+---------------------------------------+
1| i2c controller driver |
| (in BSP) |
+---------------------------------------+
+----------------------------------------+
6| Application |
+----------------------------------------+
5| RTEMS I/O Manager |
+----------------------------------------+
4|** libi2c OS adaption layer **|
+----------------------------------------+
3| high level i2c device driver |
| (EEPROM, RTC, ...) |
| (e.g. in c/src/libchip/i2c) |
+----------------------------------------+
2|** libi2c low level abstraction layer **|
+----------------------------------------+
1| i2c controller driver |
| (in BSP) |
+----------------------------------------+
This document will describe the following interfaces in separate
sections:
+9 -3
View File
@@ -75,9 +75,15 @@ void _Thread_Clear_state(
/*
* If the thread that was unblocked is more important than the heir,
* then we have a new heir. In addition, if the current thread
* is preemptible or we are waking up one of the "pseudo-ISR" system
* threads, then we need to do a context switch.
* then we have a new heir. This may or may not result in a
* context switch.
*
* Normal case:
* If the current thread is preemptible, then we need to do
* a context switch.
* Pseudo-ISR case:
* Even if the thread isn't preemptible, if the new heir is
* a pseudo-ISR system task, we need to do a context switch.
*/
if ( the_thread->current_priority < _Thread_Heir->current_priority ) {
_Thread_Heir = the_thread;