HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

e
eisa_config(1M) eisa_config(1M)
the contents of the CFG file to determine what switch or jumper settings on an
ISA board can be used to
prevent resource conflicts.
eisa_config expects to find a CFG file for each
E/ISA board connected to the workstation. The adminis-
trator is responsible for making sure that these
CFG files are present in directory /sbin/lib/eisa
.
CFG files corresponding to boards being used should always be kept in this directory. Do not remove them
after eisa_config is run the first time, because they will be needed every time the configuration is
changed, such as when a new board is added or one is removed. Do not change the file names of the
CFG
files. The file name has a specific format which is used by
eisa_config to automatically match a board
with its
CFG file.
CFG files are normally supplied by the
E/ISA board manufacturer. Two scenarios apply:
• If the
E/ISA board is supplied by HP, the
CFG file corresponding to the board is loaded into
/sbin/lib/eisa
as part of normal operating system installation. It should never be removed.
• If the
E/ISA board is not supplied by HP, install both the
CFG file and the software driver for the
board from
HP-UX-readable media supplied by the board manufacturer. Copy the
CFG
file to direc-
tory
/sbin/lib/eisa
where it must remain as long as the card is present in the system.
All
CFG files must follow a grammar specified in the EISA bus specification. The most basic building block in
the
CFG grammar is the board. Each board has several attributes including board ID (to match with a
board’s ID register), manufacturer,
ASCII
text describing what the board does, what kinds of slots the board
can go in, whether the board has a readable
ID register, and various other capability attributes.
Each file can also contain lists of board-wide resources (such as I/O registers, switches, and jumpers) and
how they should be initialized.
A board can be treated as a set of one or more functions where a given board contains a single function or
multiple functions. An example of a two-function board is one having both a serial port and a parallel
printer port. Each function has a separate block in that board’s CFG file. Each function has a name, a type,
and a set of configuration choices.
Each choice block has a name and a set of attributes. These attributes include what resources the choice
requires and whether the function is enabled or disabled by that choice. Initialization is also usually
specified within a choice. A given choice might require that certain registers be initialized to a specified
value and that switches be set in a certain way.
Configuration Processing
E/ISA configuration is handled as follows:
• eisa_config builds a conflict-free configuration, then saves the configuration in
EISA non-
volatile memory
(NVM).
• Appropriate drivers and device files must be installed before rebooting the system.
• Next time the operating system is rebooted, the HP-UX kernel initializes the specified
E/ISA boards
according to the contents of
NVM.
If a board is currently present in the system, but has no corresponding configuration data in
NVM, the EISA
board cannot be used until the eisa_config program is run again and the new board is accounted for in
NVM. A newly installed or existing E/ISA board is not usable until eisa_config has added it and the
system has been rebooted with the necessary drivers and device special files installed. See EXAMPLES for
an illustration of how to add a new board to the system.
It is possible to add EISA boards that do not have switches or jumpers to the configuration without running
eisa_config interactively. The /sbin/bcheckrc script invokes eisa_config with automatic
mode during each system initialization. If a board has been added since the last time
eisa_config was
executed,
eisa_config attempts to add the new board to the configuration. If the new board is suc-
cessfully added, the system may need to be rebooted (/sbin/bcheckrc does this automatically). If the
new board could not be added to the configuration, a warning is written to the system console and
/etc/eisa/config.err.
In addition to writing to NVM, eisa_config also automatically saves the current configuration to an SCI
file called /etc/eisa/system.sci. SCI files can also be created by the interactive
save command
(see below). The
E/ISA subsystem can also be initialized from an SCI file, rather than from NVM by using the
eisa_config -n command form discussed earlier. SCI files are quite useful when a site has several
identically-configured workstations. Run eisa_config on one system and save the configuration in an
SCI file. Copy this file to other systems, then use it to initialize those systems. Remember that the
Section 1M−−200 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005