Login or Register to Ask a Question and Join Our Community


UNIX for Advanced & Expert Users

help regarding device driver

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users help regarding device driver
# 1  
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
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. 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

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

LEARN ABOUT OSF1

cfgmgr_get_state

cfgmgr_get_state(9r)													      cfgmgr_get_state(9r)

NAME

       cfgmgr_get_state - General: Determines the configuration state

SYNOPSIS

       int cfgmgr_get_state(
	       char *driver_name,
	       int *driver_cfg_state );

ARGUMENTS

       Specifies  the  name  of  the device driver whose configuration state you want to obtain. This name is a string that matches the string you
       specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the  driver  name  (fol-
       lowed  by  a  colon)  in  the  sysconfigtab  file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
       installation.  Returns one of the following state value bits to the driver_cfg_state argument:  The  specified  device  driver  is  in  the
       dynamic	configuration  state.  This  means  the  driver was dynamically configured into the kernel.  The specified device driver is in the
       static configuration state. This means the driver was statically configured into the kernel.

DESCRIPTION

       The cfgmgr_get_state routine obtains the configuration state of the specified device driver. The specified device driver is in  either  the
       static configuration state or the dynamic configuration state.

       The  cfgmgr_get_state  routine returns the state value in the driver_cfg_state argument. Driver writers should store this state value in an
       xx_is_dynamic variable or some similarly named variable.

       You typically call the cfgmgr_get_state routine in the CFG_OP_CONFIGURE entry point of the device driver's configure routine.

RETURN VALUES

       Upon successful completion, cfgmgr_get_state returns the value ESUCCESS. This success value indicates that  cfgmgr_get_state  returned  the
       configuration state of the specified device driver in the driver_cfg_state argument. Otherwise, cfgmgr_get_state returns one of the follow-
       ing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you  specified	in
       the  driver_name  argument  does  not  exist.  In this case, cfgmgr_get_state cannot return the configuration state of the specified device
       driver in the driver_cfg_state argument.  The device driver that you specified in the driver_name argument is not a valid name.

EXAMPLES

       See Writing Device Drivers: Tutorial for a code example of the cfgmgr_get_state interface.

SEE ALSO

       Routines: cfgmgr_set_status(9r)

															      cfgmgr_get_state(9r)