|
|
Studying for the A+, Network+ or Security+ exams? Get over 2,600 pages of FREE study guides at CertiGuide.com! |
|
Join the PC homebuilding revolution! Read the all-new, FREE 200-page online guide: How to Build Your Own PC! |
|
NOTE: Using robot software to mass-download the site degrades the server and is prohibited. See here for more. Find The PC Guide helpful? Please consider a donation to The PC Guide Tip Jar. Visa/MC/Paypal accepted. |
| Take a virtual vacation any time at DesktopScenes.com - view my art photos online for FREE in either Flash or HTML! |
|
Tired of the boss? Ever wanted to be an independent freelancer? Not sure how to get started? The all-new Online Freelancing Guide can help. Tons of useful info, and it's free! Join the online freelancing revolution today. |
[ The PC Guide | Systems and Components Reference Guide | Motherboard and System Devices | System Resources | Input / Output (I/O) Addresses ] Memory-Mapped I/O You can think of I/O addresses like a bunch of small two-way "mailboxes" in the system's memory. Take for example a communications (COM) port that has a modem connected to it. When information is received by the modem, it needs to get this information into the PC. Where does it put the data it pulls off the phone line? One answer to this problem is to give each device its own small area of memory to work with. This is called memory-mapped I/O. When the modem gets a byte of data it sends it over the COM port, and it shows up in the COM port's designated I/O address space. When the CPU is ready to process the data, it knows where to look to find it. When it later wants to send information over the modem, it uses this address again (or another one near it). This is a very simple way of dealing with the problem of information exchange between devices.
|
|