File Formats devicedb(4)
NAME
devicedb - format of the device tree database file
SYNOPSIS
devicedb
DESCRIPTION
The device tree database file is an ASCII file used to
record information about hardware devices. The format is
line-oriented, with the following fields: dev_id, name,
dev_type, bus_type, bef_name, describe_dev, and properties.
Each line contains a database entry.
Records can be in an arbitrary order.
Records are terminated by newline characters, and fields are
separated by any number of spaces and tabs.
Quotes can be used in any field to allow white space.
Other than comments (lines beginning with #) and the Version
string, no other tokens are understood.
The database fields are:
dev_id List of unique device identifiers, separated by
the pipe character | when more than one ID matches
the same entry.
name The device name. When the device ID matches an
entry in the device database, the name property is
set to this value and the ``compatible'' property
is set to the device ID. If no device database
entry matched, then the node will just have the
device ID for the name property. This allows you
to specify the Solaris driver name for a device
when you know what it is. PCI devices are typi-
cally listed in the /etc/driver_aliases file, so
you just map the name back to the device ID and
let driver_aliases take care of the driver name
mapping.
dev_type The device type. Valid values are:
com Serial ports
mem Memory extender cards
mfc Multi-function card
msd Storage device, like SCSI or IDE
net Network devices
plat Platform driver
oth Miscellaneous (including sound cards)
ptr Mouse devices and so on
vid Video/graphics cards
prt Parallel ports
bus_type The bus type (such as ISA, PnP ISA,
EISA, MCA, PCI, PCMCIA, or all)
bef_name The name of the realmode driver for bootable dev-
ices; otherwise "none."
describe_dev
Free form descriptive device text.
properties
Optional additional device properties of the form
name=value, that is, ipl=3. Properties are added
to the device tree node passed to the kernel. This
field is also used to make this database ``exten-
sible.'' Properties that begin with a dollar sign
($) pass information to the Solaris (Intel Plat-
form Edition) Device Configuration Assistant pro-
gram, but are not added to the device tree. For
example, the $forceload property tells the Confi-
guration Assistant program that it must always
load the specified realmode driver in order for
that realmode driver to set additional properties
on the node.
EXAMPLES
Example 1: PCI devicedb Entry
The following example associates the pci9004,8578 pci alias
with the adp.bef realmode driver.
pci9004,8578 pci9004,8578 msd pci adp.bef "Adaptec AHA-7885 SCSI"
Example 2: PnP devicedb Entry
The following example associates several PnP (Plug and Play)
aliases with the asy Solaris serial driver, and the com.bef
realmode serial driver and indicates the driver should be
forceloaded at each machine boot.
PNP0500|PNP0501|ISY0020 asy com all com.bef "Serial port" $forceload=yes
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWpkgd |
|_____________________________|_____________________________|
| CSI | Enabled |
|_____________________________|_____________________________|
| Interface Stability | Evolving |
|_____________________________|_____________________________|
SEE ALSO
boot(1M), pkg_drv(1M), pkgadd(1M), driver.conf(4),
driver.itu(4), attributes(5).
Writing Device Drivers
SunOS 5.7 Last change: 24 May 1999
|
Print-friendly Version
