Specifications

Driver Installation and Tuning
14-3
Base kernel rebuilds are usually needed after a statically linked kernel module is installed,
when any static module is removed, or when system tunable parameters are modified.
If you execute idbuild without any options and if the environment variable $OBJ is
null or /, a flag is set and the kernel rebuild is deferred to next system reboot.
idcheck 14
The idcheck command is used to obtain selected information about the system configu-
ration. The idcheck command is designed to help driver writers determine whether a
particular driver package is already installed.
The options available for the idcheck command enable you to select which item to
check for, but it is the -p module-name option which checks for the existence of a particu-
lar DSP's modules. idcheck returns a numeric value depending on which components it
finds, or 0 if no components are found.
For complete information about the idcheck command, refer to the idcheck(1M)
manual page.
idinstall 14
idinstall is called by a package installation script or removal script to add (-a), delete
(-d), update (-u), or get (-g or -G) device driver/kernel module configuration data.
idinstall expects to find driver/module component files in the current directory.
When components are installed or updated with -a or -u option, they are copied into sub-
directories of the /etc/conf directory and then deleted from the current directory,
unless the -k flag is used to keep them.
NOTE
The Driver.o component is, by default, symbolically linked
instead of copied. The -C option is provided to force a copy.
In the simplest case of installing a new DSP, the command syntax used by the DSP's
Install script should be /etc/conf/bin/idinstall -a module-name. In this case the
command requires and installs the DSP Driver.o, Master, and System components,
and optionally installs other components, including Space.c, Stubs.c, Node, Init,
Rc, Sd, Modstub.o, Sassign, and Mtune if those files are present in the current direc-
tory.
The Driver.o, Modstub.o, Space.c, and Stubs.c components are moved to a
directory named /etc/conf/pack.d/module-name. The remaining components are
stored in directories under /etc/conf, which are organized by component type, in files
named module-name. For example, the Node file would be moved to
/etc/conf/node.d/module-name, the Master file moved to
/etc/conf/mdevice.d/module-name, and the System file moved to
/etc/conf/sdevice.d/module-name.