2
3
4
5 NAME
6 driver.conf - driver configuration files
7
8 SYNOPSIS
9 driver.conf
10
11
12 DESCRIPTION
13 Driver configuration files provide values for device properties. The
14 values override values provided by the devices themselves. Most modern
15 devices provide enough property values to make a driver configuration
16 file unnecessary.
17
18
19 The system associates a driver with its configuration file by name. For
20 example, a driver in /usr/kernel/drv called wombat has the driver
21 configuration file wombat.conf, also stored in /usr/kernel/drv,
22 associated with it. On systems capable of support 64-bit drivers, the
23 driver configuration file should be placed in the directory in which
24 the 32-bit driver is (or would be) located, even if only a 64-bit
25 version is provided. For example, a 64-bit driver stored in
26 /usr/kernel/drv/sparcv9 stores its driver configuration file in
27 /usr/kernel/drv.
28
29
30 The value of the name property is the node name. In a driver.conf file,
31 where the generic node name and compatible property associated with a
32 self-identifying devices are typically not used, the node name must be
33 a binding name. The binding name is the name chosen by the system to
34 bind a driver to the device. The binding name is either an alias
35 associated with the driver established by add_drv(1M) or the driver
36 name itself.
37
38
39 The syntax of a single entry in a driver configuration file takes one
40 of three forms:
41
42 name="node name" parent="parent name" [property-name=value ...];
43
44
45
177 property on the second node retrieves the value of the global debug-
178 level property (3).
179
180
181 SEE ALSO
182 add_drv(1M), pci(4), pseudo(4), sbus(4), scsi(4), probe(9E),
183 ddi_getlongprop(9F), ddi_getprop(9F), ddi_getproplen(9F),
184 ddi_prop_get_int(9F), ddi_prop_lookup(9F), ddi_prop_op(9F)
185
186
187 Writing Device Drivers
188
189 WARNINGS
190 To avoid namespace collisions between multiple driver vendors, it is
191 strongly recommended that the name property of the driver should begin
192 with a vendor-unique string. A reasonably compact and unique choice is
193 the vendor over-the-counter stock symbol.
194
195 NOTES
196 The update_drv(1M) command should be used to prompt the kernel to
197 reread driver.conf files. Using modunload(1M) to update driver.conf
198 continues to work in release 9 of the Solaris operating environment,
199 but the behavior will change in a future release.
200
201
202
203 January 5, 2007 DRIVER.CONF(4)
|
2
3
4
5 NAME
6 driver.conf - driver configuration files
7
8 SYNOPSIS
9 driver.conf
10
11
12 DESCRIPTION
13 Driver configuration files provide values for device properties. The
14 values override values provided by the devices themselves. Most modern
15 devices provide enough property values to make a driver configuration
16 file unnecessary.
17
18
19 The system associates a driver with its configuration file by name. For
20 example, a driver in /usr/kernel/drv called wombat has the driver
21 configuration file wombat.conf, also stored in /usr/kernel/drv,
22 associated with it. On systems that support 64-bit drivers, the driver
23 configuration file should be placed in the directory in which the
24 32-bit driver is (or would be) located, even if only a 64-bit version
25 is provided. For example, a 64-bit driver stored in
26 /usr/kernel/drv/sparcv9 stores its driver configuration file in
27 /usr/kernel/drv.
28
29
30 The value of the name property is the node name. In a driver.conf file,
31 where the generic node name and compatible property associated with a
32 self-identifying devices are typically not used, the node name must be
33 a binding name. The binding name is the name chosen by the system to
34 bind a driver to the device. The binding name is either an alias
35 associated with the driver established by add_drv(1M) or the driver
36 name itself.
37
38
39 The syntax of a single entry in a driver configuration file takes one
40 of three forms:
41
42 name="node name" parent="parent name" [property-name=value ...];
43
44
45
177 property on the second node retrieves the value of the global debug-
178 level property (3).
179
180
181 SEE ALSO
182 add_drv(1M), pci(4), pseudo(4), sbus(4), scsi(4), probe(9E),
183 ddi_getlongprop(9F), ddi_getprop(9F), ddi_getproplen(9F),
184 ddi_prop_get_int(9F), ddi_prop_lookup(9F), ddi_prop_op(9F)
185
186
187 Writing Device Drivers
188
189 WARNINGS
190 To avoid namespace collisions between multiple driver vendors, it is
191 strongly recommended that the name property of the driver should begin
192 with a vendor-unique string. A reasonably compact and unique choice is
193 the vendor over-the-counter stock symbol.
194
195 NOTES
196 The update_drv(1M) command should be used to prompt the kernel to
197 reread driver.conf files.
198
199
200
201 September 16, 2018 DRIVER.CONF(4)
|