Configuring HP-UX For Peripherals

284 AppendixC
Major and Minor Numbers
Associating a Custom Driver with a Peripheral
Associating a Custom Driver with a
Peripheral
If you are configuring HP peripherals and standard HP drivers, HP-UX
configures the elements automatically, provided the drivers have been
included in the kernel input file.
Consider, however, the scenario of having a peripheral device for which
you need to use a custom driver. Perhaps you have received the driver on
a tape, which you have loaded onto your system. If you want to associate
a driver with only a specific hardware path, you must include the driver
and the peripheral address in a "driver statement" of the /stand/system
file. You must make sure the driver can be found by the kernel-build
utility, and you must rebuild the kernel.
NOTE You can use this technique to load any sio-style driver or wsio-style
device driver. You cannot force-configure wsio-style interface drivers at a
specific address using this technique. However, you can configure
wsio-style interface drivers as long as the driver is included in the
system file and no other interface driver in the /stand/system file can
claim the card in question. For further information, refer to the Driver
Development Guide.
Step 1. Rebuild the kernel to include the added device driver, by following these
steps:
a. Change directory to the build environment (/stand/build). There,
execute a system preparation script, system_prep. system_prep
writes a system file based on your current kernel in the current
directory. (That is, it creates /stand/build/system.) The -v provides
verbose explanation as the script executes.
cd /stand/build
/usr/lbin/sysadm/system_prep -v -s system
b. Manually edit the /stand/build/system file in two places to add the
custom driver:
NOTE Do not use the kmsystem command to perform this step; edit the file