diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-EAA6A9FB-A470-550C-B7B4-FF68A733A2D5.dita
--- a/Symbian3/PDK/Source/GUID-EAA6A9FB-A470-550C-B7B4-FF68A733A2D5.dita Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-EAA6A9FB-A470-550C-B7B4-FF68A733A2D5.dita Fri Aug 13 16:47:46 2010 +0100
@@ -88,7 +88,7 @@
already have the kernel lock, or in the case of IDFCs, you do not need to
acquire it as no preemption can occur. In these cases, you just call NFastMutex::Wait() and NFastMutex::Signal(). The following diagram illustrates the general principle:
Fast mutex
-
+
There are a number of assumptions here, one of which is that the
priorities are such that thread T1 does not run until a reschedule occurs,
after T2 has been interrupted.
Example
@@ -489,7 +489,7 @@
somewhat artificial, and not based on real code, the following diagram nevertheless
shows the basic idea behind Symbian platform semaphores.
Symbian platform semaphore
-
+
Rules
There
are a few rules about the use of Symbian platform semaphores: