Motorola MCP750 Specifications Page 35

  • Download
  • Add to my manuals
  • Print
  • Page
    / 344
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 34
Understanding Device Drivers
2-11
1. Prepare a Driver Software Package (DSP), including the Driver.o object
module (the actual driver code), Master, System, and if needed
Sadapters file definitions, and other components.
2. Install the driver's DSP
3. Update the system configuration files
4. Prepare to generate a new kernel.
5. Shutdown and reboot the system. During the reboot, the system uses infor-
mation from the modified system configuration files to create special files
in /dev, and the entries for the new driver in the system initialization
tables, switch tables, and interrupt vector tables. When the system reinitial-
izes, it initializes the driver as part of the kernel.
NOTE
Loadable drivers integrate into the kernel while the system runs,
without rebooting the system and rebuilding the kernel.
Chapter 13 (“Loadable Modules”) describes how to install and
configure loadable drivers.
The Installable Driver Tools (idtools) utilities install and configure drivers. Chapter 14
(“Driver Installation and Tuning”) details installing and configuring drivers, and how the
system initializes.
Master, System, and Sadapters Files 2
The following files contain important configuration information needed to integrate a
driver into a running system:
Master
System
Sadapters (for adapter card drivers)
Master File 2
The Master file describes properties of the driver as a whole, regardless of the number of
devices supported. Once installed, the driver’s Master file resides in the directory
/etc/conf/mdevice.d. This directory contains a separate Master file for each
device driver installed. Once installed, Driver Software Packages (DSPs) should never
access these or any other idtools files directly; use idtools commands to access them.
Configuration data defined in the Master file includes the names of the driver's entry
point routines, and an alphanumeric prefix (assigned by the driver writer) prepended to the
names of the driver's routines in the system tables. The prefix enables the kernel to distin-
guish between drivers’ routine names (and other variables), avoiding conflict with other
variables in the system named alike. For example, a RAM disk driver given a prefix of
Page view 34
1 2 ... 30 31 32 33 34 35 36 37 38 39 40 ... 343 344

Comments to this Manuals

No comments