OUTB(2) Linux Programmer's Manual OUTB(2)NAME
outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - port I/O
DESCRIPTION
This family of functions is used to do low-level port input and output. The out* functions do port output, the in* functions do port
input; the b-suffix functions are byte-width and the w-suffix functions word-width; the _p-suffix functions pause until the I/O completes.
They are primarily designed for internal kernel use, but can be used from user space.
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.
CONFORMING TO
outb() and friends are hardware-specific. The value argument is passed first and the port argument is passed second, which is the opposite
order from most DOS implementations.
SEE ALSO ioperm(2), iopl(2)COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1995-11-29 OUTB(2)
Check Out this Related Man Page
OUTB(2) Linux Programmer's Manual OUTB(2)NAME
outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - port I/O
DESCRIPTION
This family of functions is used to do low-level port input and output. The out* functions do port output, the in* functions do port
input; the b-suffix functions are byte-width and the w-suffix functions word-width; the _p-suffix functions pause until the I/O completes.
They are primarily designed for internal kernel use, but can be used from user space.
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.
CONFORMING TO
outb() and friends are hardware-specific. The value argument is passed first and the port argument is passed second, which is the opposite
order from most DOS implementations.
SEE ALSO ioperm(2), iopl(2)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1995-11-29 OUTB(2)
I'm a UNIX newbie, so I know I'll be making foolish errors here...
I'm trying to set up my Mac OS X 10.2 server to serve my domain name. I've got Apache running reasonably well , and I know Sendmail is up and running...
Now, I seem to need to get BIND running for the domain name, and it... (2 Replies)
What is the correct mkfs syntax to create mirrored disk files systems? I need to make the file system 20gb. For example:
machine# mkfs -F ufs /dev/md/dsk/d40
size not specified
ufs usage: mkfs special size(sectors) \
-m : dump fs cmd line used to make this partition
-V : print this... (4 Replies)
Before I start, I'm posting this for community knowledge, not to offend anyone. I thought it was an interesting project so that's why I'm sharing it.
In the notorious erotic classified ads of craigslist, thousands of individuals post classifieds, using the internet to sell themselves with an... (0 Replies)
Hello
How do i check that correct input files are used while using AWk and SED for file manipulation?
e.g
awk '/bin/ {print $0 }' shell.txt
sed 's/hp/samsung/' printers.txt
how do i ensure that the correct input files I am working with are used? (5 Replies)