10-14-2010
Something tells me that can't be all the code.
0xcf8 is the PCI configuration address space, which Linux is almost certainly using.
What exactly is it doing or not doing?
Why are you attempting to get the parallel port I/O port? That's probably already in use, and there's far less drastic ways than writing a device driver to get to it.
Also, you have 6 posts under your belt, and surely have been told about code tags by now.
4 More Discussions You Might Find Interesting
1. Solaris
I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr
is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I have a device driver that uses UARTserial port to write/read to-from a device.
That device driver is working fine on FC3 machine( kernel version 2.6.12)...
Now I am switching to FC9 (kernel version 2.6.25.11-97).I have changed the interrupt flag SA_INTERRUPT to IRQF_DISABLED... (0 Replies)
Discussion started by: rajuprade
0 Replies
3. Programming
Hi All,
I have a device driver that uses UARTserial port to write/read to-from a device.
That device driver is working fine on FC3 machine( kernel version 2.6.12)...
Now I am switching to FC9 (kernel version 2.6.25.11-97).I have changed the interrupt flag SA_INTERRUPT to IRQF_DISABLED... (0 Replies)
Discussion started by: rajuprade
0 Replies
4. Red Hat
Hello,
Please help me if you could to resolve the problem with NVIDIA driver.
I have Lenovo T61p. I installed RHAT6 Open Client and then downloaded and installed NVIDIA driver version 270.41.06.
The product is Quadro FX 570. My laptop display type is LVDS. After installation everything works... (1 Reply)
Discussion started by: susja
1 Replies
LPT(4) BSD Kernel Interfaces Manual LPT(4)
NAME
lpt -- generic printer device driver
SYNOPSIS
device ppc
device ppbus
device lpt
DESCRIPTION
The current lpt driver is the port of the original lpt driver to the ppbus(4) system.
One purpose of this port was to allow parallel port sharing with other parallel devices. Secondly, inb()/outb() calls have been replaced by
ppbus function calls. lpt is now arch-independent thanks to the ppbus interface. See ppbus(4) for more info about the ppbus system.
The parallel port bus is allocated by lpt when the printer device is opened and released only when the transfer is completed: either when the
device is closed or when the entire buffer is sent in interrupt driven mode.
The driver can be configured to be either interrupt-driven, or to poll the printer. Ports that are configured to be interrupt-driven can be
switched to polled mode by using the lptcontrol(8) command.
Depending on your hardware, extended capabilities may be configured with the lptcontrol(8) command. With an ECP/ISA port, you can take
advantage of FIFO and DMA.
In order to retrieve printer info from /dev/lpt0, just apply the cat command to the device. If the printer supports IEEE1284 nibble mode and
has data to send to the host, you will get it.
FILES
/dev/lpt0 first parallel port driver
SEE ALSO
ppbus(4), ppc(4), lptcontrol(8)
HISTORY
This driver replaces the functionality of the lpa driver, which is now defunct.
BUGS
There are lots of them, especially in cheap parallel port implementations.
It is only possible to open a lpt port when a printer is connected and on-line, making it impossible to run lptcontrol(8) when there is no
printer connected.
This driver could still stand a rewrite.
BSD
February 14, 1999 BSD