X-Git-Url: http://pilppa.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=Documentation%2FDocBook%2Fdeviceiobook.tmpl;h=9ee6f3cbb4148b8363208328912c119dc7ee71b5;hb=5111c0753486fffde14de2b207e46760b9c05fd0;hp=90ed23df1f68f6f14c0077d7a196c36c0db08c11;hpb=1b9a3917366028cc451a98dd22e3bcd537d4e5c1;p=linux-2.6-omap-h63xx.git
diff --git a/Documentation/DocBook/deviceiobook.tmpl b/Documentation/DocBook/deviceiobook.tmpl
index 90ed23df1f6..9ee6f3cbb41 100644
--- a/Documentation/DocBook/deviceiobook.tmpl
+++ b/Documentation/DocBook/deviceiobook.tmpl
@@ -85,7 +85,7 @@
Memory Mapped IO
-
+
Getting Access to the Device
The most widely supported form of IO is memory mapped IO.
@@ -114,7 +114,7 @@
-
+
Accessing the device
The part of the interface most used by drivers is reading and
@@ -272,9 +272,9 @@ CPU B: spin_unlock_irqrestore(&dev_lock, flags)
-
+
Port Space Accesses
-
+
Port Space Explained
@@ -291,7 +291,7 @@ CPU B: spin_unlock_irqrestore(&dev_lock, flags)
-
+
Accessing Port Space
Accesses to this space are provided through a set of functions
@@ -316,7 +316,8 @@ CPU B: spin_unlock_irqrestore(&dev_lock, flags)
Public Functions Provided
-!Einclude/asm-i386/io.h
+!Iinclude/asm-x86/io_32.h
+!Elib/iomap.c