Motorola MCP750 Specifications Page 36

  • Download
  • Add to my manuals
  • Print
  • Page
    / 344
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 35
D
evice Driver Programming
2-12
ram_ results in routines named ram_open, ram_init and so on. For more informa-
tion, see the prefix(D1) manual page.
The Master file can also contain the driver's major number and various flags defining
specific characteristics of that driver (for example, whether a character or block driver).
During installation, the idtools assign a major number if the driver's Master file doesn't
specify one. For more information, see the Master(4) manual page.
System File 2
A driver's System file provides information needed to configure the driver into the next
kernel build. After installation, the driver’s System file resides in the directory
/etc/conf/sdevice.d. This directory contains a separate System file for each
device driver installed.
Configuration data defined in the System file includes a flag that indicates whether or not
the driver ought to be incorporated into the kernel. For more information, see the
System(4) manual page.
Sadapters File 2
Adriver'sSadapters file identifies and describes the functional characteristics of an
adapter card so the system can incorporate it into the next configuration built. The Mas-
ter and System files describe the adapter with general configuration information. When
the kernel module’s Driver Software Package is installed, idinstall(1M) stores the
Sadapters file information in $OBJ/etc/conf/sadapters.d/kernel.
Driver Header Files 2
Driver source code must contain some standard #include files giving the driver access
to system utilities and data structures used to return information to the kernel.
The description of each kernel utility function in the DDI/DKI manual pages indicates
which header files must be included in a driver that uses that function. Chapter 9 (“Under-
standing the Kernel Environment”) describes the standard header files typically included
in a device driver’s source file.
Driver Development 2
Device driver development requires more up-front planning than most application pro-
gramming projects. At the very least it involves more testing and debugging, and requires
more hardware knowledge. Chapter 10 (“Developing a Device Driver”) explains the full
procedure for developing device drivers. Chapter 14 (“Driver Installation and Tuning”)
describes procedures for installing device drivers. Chapter 15 (“Driver Testing and Debug-
ging”) describes the tools available for testing and debugging installed device drivers.
Page view 35
1 2 ... 31 32 33 34 35 36 37 38 39 40 41 ... 343 344

Comments to this Manuals

No comments