9 More Discussions You Might Find Interesting
1. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
2. Fedora
Greetings,
A sort of newbie question...
I would like to control a couple of stepper motors via the parallel port using C code. I have discovered in Linux, the ioperm() function is required before the outportb() function can be used to send a byte to the parallel port. My problem is ioperm()... (1 Reply)
Discussion started by: meyerga00
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am trying to add a parallel printer to my SCO OSR6 server, yet when I run mkdev parallel it just brings up the message: "Parallel Ports are configured automatically in SCO Openserver 6".
So when I try and add a local printer, no /dev/lp# ports are shown in the list, only serial ports... (1 Reply)
Discussion started by: Martyn
1 Replies
4. SCO
How do or what do I need to add PCI / PCIe (PCI Express) parallel ports add-on adapters to OpenServer 6.0.0? OpenServer 5 could see PCI slots but OpenServer 6.0.0 (Original CD or the Re-cut one) required a maintenance pack to be installed? Is this right and how do I check to see if these work? (2 Replies)
Discussion started by: uxlunatick
2 Replies
5. UNIX for Advanced & Expert Users
I am having issues with SCO recognizing my parallel port. The port is being used so I can run dialogic using a dongle for the serial number but the port is not noticed. It is turned on in the bios and should work fine but when I attempt to run the software I get errno=6 and it appears to not be... (0 Replies)
Discussion started by: shuhemizer
0 Replies
6. UNIX for Dummies Questions & Answers
I am having issues with SCO recognizing my parallel port. The port is being used so I can run dialogic using a dongle for the serial number but the port is not noticed. It is turned on in the bios and should work fine but when I attempt to run the software I get errno=6 and it appears to not be... (0 Replies)
Discussion started by: shuhemizer
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have been using a computer to keep track of inventory for my business. I am pretty sure it runs on Unix. In the back of the computer there is some sort of PCI card that has about 8 RJ-11 ports on it. I use that card to connect the Unix system to my 3 VT-220 terminals. I use a simple 6... (1 Reply)
Discussion started by: john202
1 Replies
8. Programming
Hi I'm trying to look for information about reading/writing to the parallel port of a Sun Ultra 5 running Solaris 8. I'd just like to see some basic programs written in C, nothing fancy, just reading and wrting to the port, getting the port address etc. toggling the lines.
I've tried searching... (2 Replies)
Discussion started by: fishman2001
2 Replies
9. Filesystems, Disks and Memory
is there a command so that i can se info about the parallel port, if there isn't a specific command for that is there a command so i can se info about the system and all ports and devices?
Thanx
/Nick (2 Replies)
Discussion started by: sajjan2
2 Replies
PARPORT_REGISTER_DEV(9) Parallel Port Devices PARPORT_REGISTER_DEV(9)
NAME
parport_register_device - register a device on a parallel port
SYNOPSIS
struct pardevice * parport_register_device(struct parport * port, const char * name, int (*pf) (void *), void (*kf) (void *),
void (*irq_func) (void *), int flags, void * handle);
ARGUMENTS
port
port to which the device is attached
name
a name to refer to the device
pf
preemption callback
kf
kick callback (wake-up)
irq_func
interrupt handler
flags
registration flags
handle
data for callback functions
DESCRIPTION
This function, called by parallel port device drivers, declares that a device is connected to a port, and tells the system all it needs to
know.
The name is allocated by the caller and must not be deallocated until the caller calls parport_unregister_device for that device.
The preemption callback function, pf, is called when this device driver has claimed access to the port but another device driver wants to
use it. It is given handle as its parameter, and should return zero if it is willing for the system to release the port to another driver
on its behalf. If it wants to keep control of the port it should return non-zero, and no action will be taken. It is good manners for the
driver to try to release the port at the earliest opportunity after its preemption callback rejects a preemption attempt. Note that if a
preemption callback is happy for preemption to go ahead, there is no need to release the port; it is done automatically. This function may
not block, as it may be called from interrupt context. If the device driver does not support preemption, pf can be NULL.
The wake-up ("kick") callback function, kf, is called when the port is available to be claimed for exclusive access; that is, parport_claim
is guaranteed to succeed when called from inside the wake-up callback function. If the driver wants to claim the port it should do so;
otherwise, it need not take any action. This function may not block, as it may be called from interrupt context. If the device driver does
not want to be explicitly invited to claim the port in this way, kf can be NULL.
The interrupt handler, irq_func, is called when an interrupt arrives from the parallel port. Note that if a device driver wants to use
interrupts it should use parport_enable_irq, and can also check the irq member of the parport structure representing the port.
The parallel port (lowlevel) driver is the one that has called request_irq and whose interrupt handler is called first. This handler does
whatever needs to be done to the hardware to acknowledge the interrupt (for PC-style ports there is nothing special to be done). It then
tells the IEEE 1284 code about the interrupt, which may involve reacting to an IEEE 1284 event depending on the current IEEE 1284 phase.
After this, it calls irq_func. Needless to say, irq_func will be called from interrupt context, and may not block.
The PARPORT_DEV_EXCL flag is for preventing port sharing, and so should only be used when sharing the port with other device drivers is
impossible and would lead to incorrect behaviour. Use it sparingly! Normally, flags will be zero.
This function returns a pointer to a structure that represents the device on the port, or NULL if there is not enough memory to allocate
space for that structure.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 PARPORT_REGISTER_DEV(9)