06-18-2012
It's not that it can't work in "parallel", it's that your code is deadlocking...
We cannot possibly say without seeing your code...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm way confused. I loaded RH 7.1 on an old P-75 Compaq. IT has an EtherExpress pro/100 card in it and I have that attached to the optional port on our firewall with a crossover....I can't seem to get the card to negotiate with the firewall...it's currently 100Meg at Half duplex. I'm at a loss... (3 Replies)
Discussion started by: kwalter
3 Replies
2. UNIX for Advanced & Expert Users
Hi:-
I am trying to install a device driver for Intel NIC card on TurboLinux, but getting following errors,
cc -O -Wall -o eepro100-diag eepro100-diag.c
eepro100-diag.c:72: unistd.h: No such file or directory
eepro100-diag.c:73: stdio.h: No such file or directory
eepro100-diag.c:74:... (1 Reply)
Discussion started by: s_aamir
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
If some one was to suggest, "increase your kernal tunables related to UDP, in particular the UDP send/recieve buffer size".... then what would they mean? :confused:
How can I find out what this current value is?
Thousand many thanks.
Neil (3 Replies)
Discussion started by: nhatch
3 Replies
4. IP Networking
Hi
I need to know how a driver for a network interface card works, I want to learn the basic principles since I know that every driver has its specific implementation.
For example when we speak about the scheduler, we can read an operating system book and learn general design concepts e.g.... (0 Replies)
Discussion started by: Puntino
0 Replies
5. AIX
Hi All,
I urgently need a Sample C program to Send/Recieve a file using Socket.
Thanks
Sara (1 Reply)
Discussion started by: saraperu
1 Replies
6. UNIX for Advanced & Expert Users
Hi, all:
How can I know whether the packets recieved from network by my own NIC driver are transmitted to upper layer(IP layer) or not?
How can I know if the packets come from upper layer are passed to my own NIC driver and go out further?
Is there any shell command or utility show... (9 Replies)
Discussion started by: liklstar
9 Replies
7. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
8. Solaris
Hi guys
My friend needs nfo driver for his Solaris box. I installed that driver for myself from scratch and he needs that driver in SVR4 format. I downloaded source code and run make and this is the point I don't how to proceed.
How can I recognize which needs go to the package ?
Does make... (0 Replies)
Discussion started by: solaris_user
0 Replies
9. UNIX for Advanced & Expert Users
Hi, all:
My writed NIC driver for rtl8139d adapter on linux 3.0.4 cannot send and recieve simultaneously but is able to send or recieve in parallel respectively. As soon as it send and recieve at the same time, the transmmition rate on both directions gradually decrease to zero b/s and report... (0 Replies)
Discussion started by: liklstar
0 Replies
10. Solaris
In Solaris 10 it was easy, a simple grep through modinfo output and you'd have the version of any loaded module, including your NIC drivers. In my career I've seen many people relying on this information in their scripts. Now I'm on Solaris 11, and where have the version numbers gone? The... (0 Replies)
Discussion started by: cambridge
0 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