Device driver programming


 
Thread Tools Search this Thread
The Lounge What is on Your Mind? Device driver programming
# 1  
Old 01-14-2012
Device driver programming

I want to work one day as a device driver programmer, OS I'm in love is Solaris Smilie
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 from my perspective.

I also read a solaris device driver development guide which is too advanced my knowledge, so is there some kind of book which tells how to start with system programming ?

I want to buy this book to start with system programming

http://www.amazon.com/Linux-Programm.../dp/1593272200
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Certification For Linux Device Driver Programming

Hi All, I'm looking for role change to Linux device Driver developer. My current role has no connection to Linux Device driver development and hence to support my stand i want to do a certification for the same. I have googled but couldn't found any standard certification. I have submitted... (1 Reply)
Discussion started by: kg_gaurav
1 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. 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

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

5. UNIX for Advanced & Expert Users

Kernel and Device Driver Programming

I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help. If you know, please email me at *removed* or leave a post here Regards, Farhan (0 Replies)
Discussion started by: Farhan
0 Replies
Login or Register to Ask a Question
gvid_no_claim_dev(5)						File Formats Manual					      gvid_no_claim_dev(5)

NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim VALUES
Failsafe Default Allowed values Recommended values Specific to the device you wish to prevent from claiming. DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim. The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics driver to claim their own graphics device. The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32 bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID or Device ID can use a wildcard value of For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID. Who Is Expected to Change This Tunable? Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics driver for their own hardware. Restrictions on Changing Changes to this tunable take effect at the next reboot. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters gvid_no_claim_dev(5)