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
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)
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)
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)
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)
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)
IEEE1394IF(4) BSD Kernel Interfaces Manual IEEE1394IF(4)NAME
ieee1394if -- IEEE1394 High-performance Serial Bus
SYNOPSIS
ieee1394if* at fwohci?
DESCRIPTION
NetBSD provides machine-independent bus support and raw drivers for IEEE1394 interfaces.
The ieee1394if driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)).
The ieee1394if bus attaches to the controller. Additional drivers can be attached to the bus.
Up to 63 devices, including the host itself, can be attached to a IEEE1394 bus. The root node is dynamically assigned with a PHY device
function. Also, the other IEEE1394 bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
dynamically assigned, after bus reset is initiated. On the ieee1394if bus, every device is identified by an EUI 64 address.
FILES
/dev/fw0.0
/dev/fwmem0.0
SEE ALSO fwip(4), fwohci(4), pci(4), sbp(4), fwctl(8), sysctl(8)HISTORY
The ieee1394if driver first appeared in FreeBSD 5.0, as firewire. It was added to NetBSD 4.0 under its present name.
AUTHORS
The ieee1394if driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project. It was added to NetBSD 4.0 by
KIYOHARA Takashi.
BUGS
See fwohci(4) for security notes.
BSD June 18, 2005 BSD
