Kernel and Device Driver Programming


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Kernel and Device Driver Programming
# 1  
Old 07-26-2004
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

Last edited by Perderabo; 04-06-2005 at 01:05 PM.. Reason: Remove email address
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. 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

3. Fedora

Is Kernel module is the same as a device driver?

I have been reading prep questions for my second unix academy exam, and there's a nuance, I'm not sure I understand it correctly. I've been under impression from my readings of book by Evi Nemeth and from unix academy DVDs I've been watching, that kernel's modules are drivers. I think of it, as... (25 Replies)
Discussion started by: newlinuxuser1
25 Replies

4. Linux

Linux Device Driver: avoid mem copy from/to user/kernel space

I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel. 1. The user space process makes an IOCTL call with pointer to a user memory buffer. 2. The kernel device driver in the big switch-case of IOCTL,... (1 Reply)
Discussion started by: agaurav
1 Replies

5. 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
sane-find-scanner(1)					      General Commands Manual					      sane-find-scanner(1)

NAME
sane-find-scanner - find SCSI and USB scanners and their device files SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-f] [devname] DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and some USB scanners and determine their Unix device files. It's part of the sane- backends package. For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So sane-find- scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend. For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner are tested. The files are opened and the vendor and device ids are determined if the operating system supports this feature. Currently USB scanners are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test, sane- find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners, so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner will even find USB scanners, that are not supported by any SANE backend. sane-find-scanner won't find parallel port scanners, or scanners connected to proprietary ports. OPTIONS
-h, -? Prints a short usage message. -v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa- tion and the USB device descriptors are also printed. -q Be quiet. Print only the devices, no comments. -f Force opening all explicitely given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determing the device type. devname Test device file "devname". No other devices are checked if devname is given. EXAMPLE
sane-find-scanner -v Check all SCSI and USB devices for available scanners and print a line for every device file. sane-find-scanner /dev/scanner Look for a (SCSI) scanner only at /dev/scanner and print the result. SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5) AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor and device ids only works with Linux or libusb. SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX. BUGS
No support for parallel port scanners yet. 15 Sep 2002 sane-find-scanner(1)