| ??? 07/14/07 08:34 Read: times |
#141869 - Memory Mapped I/O Responding to: ???'s previous message |
Jan Waclawek said:
The common example murmurs something about interrupts, but for them obviously also atomicity is needed - what is the point of splitting these two things? It was introduced for memory mapped I/O I think. The C standard takes a realtime clock as an example. The hardware should take care of atomicity as no program code can guarantee it. Disabling all interrupts does not help in this case. Ever tried to read a running timer/counter? |
| Topic | Author | Date |
| more to atomicity and such | 01/01/70 00:00 | |
| Interesting example ... | 01/01/70 00:00 | |
| which I did | 01/01/70 00:00 | |
| Aside: Keil - Atomic functions | 01/01/70 00:00 | |
| If you can afford it. | 01/01/70 00:00 | |
| volatile | 01/01/70 00:00 | |
| does this have some formal definition? | 01/01/70 00:00 | |
| sequence points and side effects | 01/01/70 00:00 | |
| what's exactly the value of volatile, then? | 01/01/70 00:00 | |
| example | 01/01/70 00:00 | |
| bu what is it good for then? | 01/01/70 00:00 | |
| Ok, visualize this one | 01/01/70 00:00 | |
| within a loop | 01/01/70 00:00 | |
| Memory Mapped I/O | 01/01/70 00:00 | |
OK I see it now, thanks. | 01/01/70 00:00 | |
| volatile switch | 01/01/70 00:00 |