60                      describes a possible SBus interrupt level that the device
  61                      might generate.
  62 
  63                      The driver can refer to the elements of this array by
  64                      index, and register interrupt handlers with the system
  65                      using ddi_add_intr(9F). The index into the array is
  66                      passed as the inumber argument of ddi_add_intr().
  67 
  68 
  69        registers
  70                      An arbitrary length array where each element of the array
  71                      consists of a 3-tuple of integers.  Each array element
  72                      describes a logically contiguous mappable resource on the
  73                      SBus.
  74 
  75                      The first integer of each tuple should be set to -1,
  76                      specifying that any SBus slot may be matched. The second
  77                      integer of each 3-tuple specifies the offset in the slot
  78                      address space identified by the first element.  The third
  79                      integer of each 3-tuple specifies the size in bytes of
  80                      the mappable resoure.
  81 
  82                      The registers property can only be used to augment an
  83                      incompletely specified reg property with information from
  84                      a driver configuration file.  It may only be specified in
  85                      a driver configuration file.
  86 
  87 
  88 
  89        All SBus devices must provide reg properties to the system. The first
  90        two integer elements of the reg property are used to construct the
  91        address part of the device name under /devices.
  92 
  93 
  94        Only devices that generate interrupts need to provide interrupts
  95        properties.
  96 
  97 
  98        Occasionally, it may be necessary to override or augment the
  99        configuration information supplied by the SBus device. This can be
 100        achieved by writing a driver configuration file that describes a

  60                      describes a possible SBus interrupt level that the device
  61                      might generate.
  62 
  63                      The driver can refer to the elements of this array by
  64                      index, and register interrupt handlers with the system
  65                      using ddi_add_intr(9F). The index into the array is
  66                      passed as the inumber argument of ddi_add_intr().
  67 
  68 
  69        registers
  70                      An arbitrary length array where each element of the array
  71                      consists of a 3-tuple of integers.  Each array element
  72                      describes a logically contiguous mappable resource on the
  73                      SBus.
  74 
  75                      The first integer of each tuple should be set to -1,
  76                      specifying that any SBus slot may be matched. The second
  77                      integer of each 3-tuple specifies the offset in the slot
  78                      address space identified by the first element.  The third
  79                      integer of each 3-tuple specifies the size in bytes of
  80                      the mappable resource.
  81 
  82                      The registers property can only be used to augment an
  83                      incompletely specified reg property with information from
  84                      a driver configuration file.  It may only be specified in
  85                      a driver configuration file.
  86 
  87 
  88 
  89        All SBus devices must provide reg properties to the system. The first
  90        two integer elements of the reg property are used to construct the
  91        address part of the device name under /devices.
  92 
  93 
  94        Only devices that generate interrupts need to provide interrupts
  95        properties.
  96 
  97 
  98        Occasionally, it may be necessary to override or augment the
  99        configuration information supplied by the SBus device. This can be
 100        achieved by writing a driver configuration file that describes a