Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

inl_p(2) [redhat man page]

OUTB(2) 						     Linux Programmer's Manual							   OUTB(2)

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 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. 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 port and value arguments are in the opposite order to most DOS implementations. SEE ALSO
ioperm(2), iopl(2) 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)
Man Page

4 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

formatting a Compact Flash in DOS format

:confused: I tryied to use the mount Command (and the msdos.utils) in Darwin 1.4 (OS X) to format a Compact Flash in DOS Format (I had already this native format but I changed it with Disk Utility in MacOS standard and the PC Card slot of a Windows 98-Laptop can't nore read the card) I want to... (1 Reply)
Discussion started by: dreamsurfer
1 Replies

2. UNIX for Advanced & Expert Users

more than 1 vi editor

Hi, What's the process to open 2 vi editor at a same time. Plz let me know. Thanx (5 Replies)
Discussion started by: reply2soumya
5 Replies

3. Debian

Problem on X

Hi folks, Debian 5.0 workstation PC freezes frequently on playing YouTube. This is graphic driver problem. The PC has another HD running Ubuntu 9.04. It had similar problem. After disable the driver on; System -> Administration - Hardware Device Drivers problem gone. But I can't... (3 Replies)
Discussion started by: satimis
3 Replies

4. Hardware

HP Compaq 6710 - Intel(R) PRO/Wireless 3945ABG/BG

Hi gurus, I am trying make wireless card working but I am stuck. Tried following: Hardware button for wifi is enabled (wifi led lights): # modprobe -r iwl3945 # modprobe iwl3945 # ifconfig wlan0 up SIOCSIFFLAGS: No such device # ifup wlan0 /sbin/ifup: configuration for wlan0 not... (2 Replies)
Discussion started by: wakatana
2 Replies