Differences between version 2 and revision by previous author of outb(2).
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
Newer page: | version 2 | Last edited on Sunday, March 16, 2003 6:19:00 pm | by PerryLorier | Revert |
Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:23:44 am | by perry | Revert |
@@ -1,45 +1,16 @@
-OUTB
-!!!OUTB
-NAME
-DESCRIPTION
-CONFORMING TO
-SEE ALSO
-----
!!NAME
-
-
-
outb, outw, outl, outsb, outsw, outsl - port output
-inb, inw, inl, insb, insw, insl - port input
-outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - paused I/O
+outb, outw, outl, outsb, outsw, outsl - port output%%%
+inb, inw, inl, insb, insw, insl - port input%%%
+outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - paused I/O%%%
!!DESCRIPTION
+This family of functions is used to do low level port input and output. They are primarily designed for internal kernel use, but can be used from user space, given the following information ''in addition'' to that given in ''outb(9)''
-
-This family of functions is used to do low level port input
-and output. They are primarily designed for internal kernel
-use, but can be used from user space, given the following
-information ''in addition'' to that given in
-''outb(9)''
-
-
-
You compile with __-O__ or __-O2__ or similar. The
-
functions are defined as inline macros, and will not be
-
substituted in without optimization enabled, causing
+You compile with __-O__ or __-O2__ or similar. The functions are defined as inline macros, and will not be substituted in without optimization enabled, causing
unresolved references at link time.
-
-
You use ''ioperm(2)'' or alternatively ''iopl(2)'' to
-
tell the kernel to allow the user space application to
-
access the I/O ports in question. Failure to do this will
-cause
the application to receive a segmentation
-
fault.
+You use ''ioperm(2)'' or alternatively ''iopl(2)'' to tell the kernel to allow the user space application to access the I/O ports in question. Failure to do this will because
the application to receive a segmentation fault.
!!CONFORMING TO
+__outb__ and friends are hardware specific. The ''port'' and ''value'' arguments are in the opposite order to most DOS implementations.
-
-__outb__ and friends are hardware specific. The
-''port'' and ''value'' arguments are in the opposite
-order to most DOS implementations.
!!SEE ALSO
-
-
ioperm(2), iopl(2)
-----