LYCOS RETRIEVER 
Drivers (Programming): Manuals
built 655 days ago
Unlike Linux, Solaris drivers do not access data structures such as inodes or files. In general, the only drivers should only access structures passed into entry points, structures that the driver itself declares, and structures specified by the DDI (manual section 9s). This allows kernel structures to change over time without needing to make changes to the driver. Fields within kernel data structures that a driver might need (for instance, the current location of read/write in a device), are arguments to functions, not the structures themselves. If you think you need access to kernel structures outside of the DDI/DKI, you are probably not using the DDI/DKI correctly. Of course, source code access makes all structures and kernel routines "visible" to a programmer.
Source:
Class drivers know how to communicate with a specific device class. RTUSB-32 comes with class drivers for mice, touch screens, keyboards, printers, disks, and Ethernet. Their respective APIs are documented in the RTUSB-32 Reference Manual. A USB hub class driver is integrated in the USB protocol stack and has no API.
Source:
This manual contains information systems engineers need to write device drivers that operate on the VMEbus. The manual describes VMEbus-specific topics, including VMEbus architecture and kernel interfaces that VMEbus device drivers use. A VMEbus device driver example illustrates the use of these kernel interfaces.
Source:
MORE ABOUT
Manuals