Specifications

D
evice Driver Programming
14-20
Updating a DSP 14
If a check for the existence of the DSP (using idcheck) turns up positive, a
postinstall script should use the idinstall update option. This is assuming that it
makes sense to update the DSP, and in any event, you should require a positive verifica-
tion, or at least give the user the option of aborting, before updating an existing DSP.
The following examples update a DSP:
idinstall -P pkgname -u module-name
The command overwrites all the files of the original DSP with files of the new DSP,
requiring that the module-name specified is currently installed. This command requires
that the module specified is currently installed.
For complete information about the idinstall command, refer to the
idnstall(1M) manual page.
Modifying a Kernel Parameter 14
The idtune command is used to modify system-tunable parameter. If the driver package
you are building requires modifying a parameter value, you should use the idtune com-
mand only.
NOTE
Package scripts should never access /etc/conf/mtune.d or
/etc/conf/cf.d/stune files directly; only the idinstall
and idtune commands should be used.
The idtune command takes individual system parameters, verifies that the new value is
within the upper and lower bounds specified in Mtune, searches the stune file, and mod-
ifies an existing value or adds the parameter to stune if not defined.
By default, parameters tuned using idtune do not take effect until the entire kernel is
rebuilt and rebooted. Any change made using the idtune command with the -c option
affects all the loadable kernel modules subsequently configured into the running system.
Removing a DSP 14
To remove a DSP from the system, a preremove script needs to call the idinstall
command with the -d option. An example command follows.
idinstall -P pkgname -d module-name
In the example, pkgname is the name of the package and module-name is the name of the
DSP to be removed. Once executed, all files and commands associated with the DSP are