regarding device driver


 
Thread Tools Search this Thread
Top Forums Programming regarding device driver
# 1  
Old 09-08-2008
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....
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

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

2. UNIX for Advanced & Expert Users

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... (0 Replies)
Discussion started by: rajuprade
0 Replies

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

4. 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
Login or Register to Ask a Question
clone(7)						 Miscellaneous Information Manual						  clone(7)

NAME
clone - opens a major and minor device pair on a STREAMS driver DESCRIPTION
The driver is a "pass through" device driver that allows other drivers to select unique minor device numbers on each In effect, the driver passes an open operation through to the other driver. This mechanism allows for multiple instantiations of a driver, each with a different minor number, through a single device file. When the driver is opened, it is passed a major and minor device number by the operating system. The major number is the driver's major number (72), and the minor number is the major number of the driver the user wishes to clone (referred to here as the target driver). The driver calls the open routine of the target driver with the flag which specifies a clone open. The target driver's open routine allocates an unused minor number. The target driver must use to make a new device number for the newly created device, and must set to the new device number returned by The new device number is returned to the open through The open then returns to the user a file descriptor that points to the new instantiation of the target driver. The driver is an example of a clonable driver. Notes It is not possible to do multiple opens of a device with the same major and minor number using the driver. This is because the driver is only given the major number of the driver to be cloned, and that driver will then select a minor number which has not been opened. When called with a pathname which corresponds to the clonable driver, will return different results than when it is called on a file descriptor returned from of the same clonable driver pathname. RETURN VALUES
If the driver is given an invalid minor number, or if the driver indicated is not a clonable driver, the fails and is set to [ENXIO]. SEE ALSO
open(2), fstat(2). clone(7)