Drvmap(4) Drvmap(4)
NAME
Drvmap - hardware driver description file
SYNOPSIS
Drvmap
DESCRIPTION
One of the Installable Driver/Tunable Parameters kernel
configuration files, the Drvmap file is an optional per-module
file that contains descriptions of a hardware driver and the
board(s) it supports. This file also indicates whether a
driver supports auto-configuration. It is used by the Device
Configuration Utility [dcu(1M)] as well as the kernel
configuration tools.
Blank lines and lines beginning with ``#'' or ``*'' are
considered comments and are ignored. Multiple fields on a
line are separated by vertical bars (``|'').
The first non-comment line of a Drvmap file contains the
following per-driver fields:
drvname|autoconf|verify|category|brand
where:
drvname
specifies the name of the driver module as it
appears in its Master file.
autoconf
specifies whether the driver supports auto-
configuration; ``Y'' indicates support and ``N''
indicates that auto-configuration is not
supported.
verify specifies whether the driver provides a verify
routine to assist auto-configuration; ``Y''
indicates the presence of a verify routine, ``V''
indicates the presence of a verify routine that
must be invoked automatically by DCU before it
assigns the driver to a device, and ``N''
indicates the absence of the routine.
Copyright 1994 Novell, Inc. Page 1
Drvmap(4) Drvmap(4)
category
describes the category of boards that the driver
supports. It is a string that can include spaces
but no vertical bars.
Typical entries for category include:
Network Interface Cards
Host Bus Adapters
Communications Cards
Video Cards
Sound Boards
Miscellaneous
brand identifies the overall manufacturer name or
``brand name'' of the boards that are supported
by the driver. This is a string that can include
spaces but no vertical bars. Brand
identification allows one or more drivers to be
grouped together at a finer granularity than
category, but at a higher level than individual
board types.
Following the driver information line is a line for each board
type supported by the driver:
|bus_type|board_id|board_name
where:
bus_type
specifies the type of bus with which the board is
used.
Valid entries for bus_type are:
SYSTEM
ISA
EISA
MCA
PCI
board_id
specifies the board ID of the supported board(s).
This is an optional field that can include spaces
but no vertical bars. Board ID strings are
specific for each bus type. Some boards and/or
Copyright 1994 Novell, Inc. Page 2
Drvmap(4) Drvmap(4)
bus types may not have board IDs; for these, the
board ID should be null. Each board ID in a
Drvmap file must be unique. The wildcards * and
? can be used in a Drvmap entry.
For example:
|ISA||Board Foo
EISA board IDs are in uncompressed form.
MCA board IDs are in the form:
0xDDDD
where each D is a hex digit, 0 - 9 or A - F. MCA
board IDs must be four digits; when necessary
leading zeroes must be used. For example:
0xABC is not correct.
0x0ABC is correct.
PCI board IDs are in the form:
0xVVVVDDDD
where V and D are hex digits, 0 - 9 or A - F,
VVVV is the vendor ID and DDDD is the device ID.
board_name
specifies the name of the supported board(s) in a
form that a user is likely to recognize. This is
a string that can include spaces but no vertical
bars.
Note that board lines are distinguished from driver lines by
the initial vertical bar.
Each of the category, brand, and board_name fields can be a
simple string or a message catalog reference in the following
format:
:msgfile:msgnum:string
Copyright 1994 Novell, Inc. Page 3
Drvmap(4) Drvmap(4)
where msgfile, msgnum, and string are the message catalog
filename, the message number, and the default (English) string
as expected by gettxt(1). The initial colon, :, distinguishes
catalog references from simple strings.
REFERENCES
dcu(1M), gettxt(1), idbuild(1M), idinstall(1M), Master(4)
Copyright 1994 Novell, Inc. Page 4