Managing and Developing Dynamically Loadable Kernel Modules

Managing and Developing Dynamically Loadable Kernel Modules
Developing Dynamically Loadable Kernel Modules
Chapter 12 535
or both of two keywords:
stub which, by its presence, indicates that the module
has stub.
phases n where n is figured by computing the logical OR of
the following mask value:
0x01 Phase 1 of the boot sequence
0x02 Phase2 of the boot sequence
0x04 Runtime
The absence of this keyword indicates that the
module supports only runtime loading (equivalent
to phases 0x04).
❏ $INTERFACE – identifies the interface names and versions on which
the module is built. For HP-UX 11.0 and later releases, enter a single
line containing the word base.
❏ $TYPE – indicates the module type and the type specific information.
Valid types are wsio_class, wsio_intfc, streams_mod,
streams_drv, and misc.
❏ Other sections (if required) – $DRIVER_DEPENDENCY, $TUNABLE, and
$DRIVER_INSTALL:
In the $DRIVER_DEPENDENCY section, enter the names of all other
modules that depend upon this module.
In the $TUNABLE section, enter the names and default values of the
tunable parameters (variables) for the module. You may also enter
minimum values for tunable parameters.
In the $DRIVER_INSTALL section, enter the module’s name and
associated block and/or character major device number(s). To have
the system dynamically assign a major number to your module,
specify -1 in both the block major and char major fields of
$DRIVER_INSTALL.
For complete details on the use of these keywords, see the “Modular
Master File” section of the master (4) manpage.