Symbian3/PDK/Source/GUID-1D3E61BD-C09D-51FD-A10B-22392FDAEFEC.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e
--- a/Symbian3/PDK/Source/GUID-1D3E61BD-C09D-51FD-A10B-22392FDAEFEC.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-1D3E61BD-C09D-51FD-A10B-22392FDAEFEC.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -103,7 +103,7 @@
 <section id="GUID-CA1BB80F-5A1C-5B66-8091-84625A0A9CFB"><title>Peripheral
 power state diagram and transitions</title> <fig id="GUID-A1F2E1D2-FA3B-55C3-B7A3-1AECBDC37453">
 <title>Peripheral power state diagram</title>
-<image href="GUID-E55B594F-CC84-5984-9307-9819F6EBEB7F_d0e389916_href.png" placement="inline"/>
+<image href="GUID-E55B594F-CC84-5984-9307-9819F6EBEB7F_d0e395769_href.png" placement="inline"/>
 </fig> <p>It can be assumed that when the peripheral driver is loaded, the
 peripheral is put into the <i>Low Power</i> state. If a new request is asserted
 on that peripheral driver from a user of that peripheral (which can include
@@ -125,6 +125,6 @@
 the power manager so requests. It can be moved back to the <i>Operational
 Power</i> state on an internal event (Interrupt, Timer). </p> <fig id="GUID-C5AED7DE-18A1-5FBF-B1E4-44067F246CC2">
 <title>Peripheral power states</title>
-<image href="GUID-EFEACBE5-B9E1-5315-88CA-DA3B7C1BFCE0_d0e389963_href.png" placement="inline"/>
+<image href="GUID-EFEACBE5-B9E1-5315-88CA-DA3B7C1BFCE0_d0e395816_href.png" placement="inline"/>
 </fig> </section>
 </conbody></concept>
\ No newline at end of file