Kernel and Device Driver Programming

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

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

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

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

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

LEARN ABOUT FREEBSD

padlock

PADLOCK(4)						   BSD Kernel Interfaces Manual 						PADLOCK(4)

NAME

     padlock -- driver for the cryptographic functions and RNG in VIA C3, C7 and Eden processors

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device crypto
	   device padlock

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   padlock_load="YES"

DESCRIPTION

     The C3 and Eden processor series from VIA include hardware acceleration for AES.  The C7 series includes hardware acceleration for AES, SHA1,
     SHA256 and RSA.  All of the above processor series include a hardware random number generator.

     The padlock driver registers itself to accelerate AES operations and, if available, HMAC/SHA1 and HMAC/SHA256 for crypto(4).  It also regis-
     ters itself to accelerate other HMAC algorithms, although there is no hardware acceleration for those algorithms.	This is only needed so
     padlock can work with ipsec(4).

     The hardware random number generator supplies data for the kernel random(4) subsystem.

SEE ALSO

     crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9)

HISTORY

     The padlock driver first appeared in OpenBSD.  The first FreeBSD release to include it was FreeBSD 6.0.

AUTHORS

     The padlock driver with AES encryption support was written by Jason Wright <jason@OpenBSD.org>.  It was ported to FreeBSD and then extended
     to support SHA1 and SHA256 by Pawel Jakub Dawidek <pjd@FreeBSD.org>.  This manual page was written by Christian Brueffer
     <brueffer@FreeBSD.org>.

BSD
								 February 8, 2010							       BSD

UNIX for Advanced & Expert Users