Sponsored Content
Full Discussion: help regarding device driver
Top Forums UNIX for Advanced & Expert Users help regarding device driver Post 302233581 by rajuprade on Monday 8th of September 2008 04:58:14 AM
Old 09-08-2008
help regarding device driver

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 for FC9.
device driver is compiling & loading properly.My program is able to send the data as well as device is also responding but I m not able to get the data inside the PC.According to me ,recieve data line interrupt is not able to get CPU attention in properly time.may be I have to increase the priority of IRQ4.
so plz tell me how to increase the priority of IRQ4 in FC9 or any other solutuion...
Thnx in advance....

regards,
Raj
 

4 More Discussions You Might Find Interesting

1. Solaris

SUNWglmr -- rasctrl environment monitoring driver for i2c or SCSI device driver ?

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. Programming

Network device driver

HI, I am writing a network device driver for RTL8139c card on 2.6.18 kernel ... I am facing few queries listed below 1. Can i able to at all write a driver for RTL8139C or Realtek had designed new chip for 2.6 series kernel? 2. If no then which driver file 2.6.18 uses .. Is it 8139too.c or... (1 Reply)
Discussion started by: niketan
1 Replies

3. Programming

regarding device driver

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. What is on Your Mind?

Device driver programming

I want to work one day as a device driver programmer, OS I'm in love is Solaris :D I am learning C in my free time which I don't have because college took my life and I need to study to pass. In college we work in C++ / Java. These languages aren't inteded for device driver programming , saying... (0 Replies)
Discussion started by: solaris_user
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
All times are GMT -4. The time now is 12:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy