Print this page
9842 man page typos and spelling

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man4/driver.conf.4
          +++ new/usr/src/man/man4/driver.conf.4
   1    1  '\" te
   2    2  .\"  Copyright (c) 2005, Sun Microsystems, Inc. All Rights Reserved
   3    3  .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4    4  .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5    5  .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6      -.TH DRIVER.CONF 4 "Jan 5, 2007"
        6 +.TH DRIVER.CONF 4 "Sep 16, 2018"
   7    7  .SH NAME
   8    8  driver.conf \- driver configuration files
   9    9  .SH SYNOPSIS
  10   10  .LP
  11   11  .nf
  12   12  \fBdriver.conf\fR
  13   13  .fi
  14   14  
  15   15  .SH DESCRIPTION
  16      -.sp
  17   16  .LP
  18   17  Driver configuration files provide values for device properties. The values
  19   18  override values provided by the devices themselves. Most modern devices provide
  20   19  enough property values to make a driver configuration file unnecessary.
  21   20  .sp
  22   21  .LP
  23   22  The system associates a driver with its configuration file by name. For
  24   23  example, a driver in \fB/usr/kernel/drv\fR called \fBwombat\fR has the driver
  25   24  configuration file \fBwombat.conf\fR, also stored in \fB/usr/kernel/drv\fR,
  26      -associated with it. On systems capable of support 64-bit drivers, the driver
       25 +associated with it. On systems that support 64-bit drivers, the driver
  27   26  configuration file should be placed in the directory in which the 32-bit driver
  28   27  is (or would be) located, even if only a 64-bit version is provided. For
  29   28  example, a 64-bit driver stored in \fB/usr/kernel/drv/sparcv9\fR stores its
  30   29  driver configuration file in \fB/usr/kernel/drv\fR.
  31   30  .sp
  32   31  .LP
  33   32  The value of the \fBname\fR property is the node name. In a \fBdriver.conf\fR
  34   33  file, where the generic node name and \fBcompatible\fR property associated with
  35   34  a self-identifying devices are typically not used, the node name must be a
  36   35  binding name. The binding name is the name chosen by the system to bind a
↓ open down ↓ 158 lines elided ↑ open up ↑
 195  194  Two global driver properties are created, \fBwhizzy-mode\fR (which has the
 196  195  string value "on") and \fBdebug-level\fR (which has the value 3). If the driver
 197  196  looks up the property \fBwhizzy-mode\fR on either node, it retrieves the value
 198  197  of the global \fBwhizzy-mode\fR property ("on"). If the driver looks up the
 199  198  \fBdebug-level\fR property on the first node, it retrieves the value of the
 200  199  \fBdebug-level\fR property on that node (1). Looking up the same property on
 201  200  the second node retrieves the value of the global \fBdebug-level\fR property
 202  201  (3).
 203  202  
 204  203  .SH SEE ALSO
 205      -.sp
 206  204  .LP
 207  205  \fBadd_drv\fR(1M), \fBpci\fR(4), \fBpseudo\fR(4), \fBsbus\fR(4), \fBscsi\fR(4),
 208  206  \fBprobe\fR(9E), \fBddi_getlongprop\fR(9F), \fBddi_getprop\fR(9F),
 209  207  \fBddi_getproplen\fR(9F), \fBddi_prop_get_int\fR(9F),
 210  208  \fBddi_prop_lookup\fR(9F), \fBddi_prop_op\fR(9F)
 211  209  .sp
 212  210  .LP
 213  211  \fIWriting Device Drivers\fR
 214  212  .SH WARNINGS
 215      -.sp
 216  213  .LP
 217  214  To avoid namespace collisions between multiple driver vendors, it is strongly
 218  215  recommended that the \fIname\fR property of the driver should begin with a
 219  216  vendor-unique string. A reasonably compact and unique choice is the vendor
 220  217  over-the-counter stock symbol.
 221  218  .SH NOTES
 222      -.sp
 223  219  .LP
 224  220  The \fBupdate_drv\fR(1M) command should be used to prompt the kernel to reread
 225      -\fBdriver.conf\fR files. Using \fBmodunload\fR(1M) to update \fBdriver.conf\fR
 226      -continues to work in release 9 of the Solaris operating environment, but the
 227      -behavior will change in a future release.
      221 +\fBdriver.conf\fR files.
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX