Christian Stueble <stueble@amaunet.cs.uni-dortmund.de> writes:
I think Fiasco/L4 uses memory mapped I/O, not separated I/O?
Memory-mapped I/O (that is, I/O via memory accesses in the virtual address space) and I/O via the separate 16-bit I/O address space (with in/out instructions; ``port I/O'') are completely separate from each other. It is not possible to map the port address space into the virtual memory, and that means it is not possible to replace port I/O with memory-mapped I/O. That's why, the kernel needs to support port I/O. Michael -- hohmuth@innocent.com, hohmuth@inf.tu-dresden.de http://home.pages.de/~hohmuth/
Am Fre, 22 Okt 1999 schrieben Sie:
Christian Stueble <stueble@amaunet.cs.uni-dortmund.de> writes:
I think Fiasco/L4 uses memory mapped I/O, not separated I/O?
Memory-mapped I/O (that is, I/O via memory accesses in the virtual address space) and I/O via the separate 16-bit I/O address space (with in/out instructions; ``port I/O'') are completely separate from each other. It is not possible to map the port address space into the virtual memory, and that means it is not possible to replace port I/O with memory-mapped I/O. That's why, the kernel needs to support port I/O. Yes, but I thought an IBM PC uses sepatated I/O, but also maps them into the memory. (A Linux docu said, that new device drivers use memory mapped I/O.. ). Books about PCs describe separated I/O only, so I think this was wrong.
-Chris-
Michael -- hohmuth@innocent.com, hohmuth@inf.tu-dresden.de http://home.pages.de/~hohmuth/
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble@ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
participants (2)
-
Christian Stueble -
Michael Hohmuth