1# 2# CDDL HEADER START 3# 4# The contents of this file are subject to the terms of the 5# Common Development and Distribution License (the "License"). 6# You may not use this file except in compliance with the License. 7# 8# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 9# or http://www.opensolaris.org/os/licensing. 10# See the License for the specific language governing permissions 11# and limitations under the License. 12# 13# When distributing Covered Code, include this CDDL HEADER in each 14# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 15# If applicable, add the following below this CDDL HEADER, with the 16# fields enclosed by brackets "[]" replaced with your own identifying 17# information: Portions Copyright [yyyy] [name of copyright owner] 18# 19# CDDL HEADER END 20# 21# Copyright 2009 Sun Microsystems, Inc. All rights reserved. 22# Use is subject to license terms. 23# 24 25# 26# Portions Copyright (c) Siemens 1999 27# All rights reserved. 28# 29 30# WARNING: enabling this driver may impact the security and data integrity of 31# devices on your system. Please refer to sgen(7d) for details. 32# 33# There are two ways of configuring sgen: by establishing an association 34# between a compatible alias for a device and the sgen driver via 35# "add_drv -i", or by using this file (sgen.conf). 36 37#--------------------------add_drv binding method----------------------------- 38# SCSI target devices are now self-identifying in Solaris. Add_drv is the 39# preferred method to control driver binding, it avoids issues associated 40# with multiple driver.conf files associating more than one driver with a 41# device. The compatible property forms for SCSI target devices used in the 42# add_drv command are described in scsi(4). 43# 44# USAGE EXAMPLE (add_drv) 45# 46# In this example, sgen is configured to bind to all scanner and ocrw devices 47# in the system, as well as the UltraToast 4000 disk from ACME using the 48# add_drv configuration method. 49# 50# add_drv -i \ 51# '"scsiclass,06" "scsiclass,0f" "scsiclass,00.vACME,pUltraToast_4000"' sgen 52 53#-------------------------sgen.conf binding method---------------------------- 54# NOTE: Support for sgen.conf configuration may be removed in a future release 55# of Solaris. 56# 57# The the remainder of this file is concerned with the .conf file 58# configuration method. Sgen may be configured to bind to SCSI devices 59# exporting a particular device type, using the device-type-config-list, which 60# is a ',' delimited list of strings. 61# 62#device-type-config-list= 63# "direct" (type 0x00) 64# "sequential" (type 0x01) 65# "printer" (type 0x02) 66# "processor" (type 0x03) 67# "worm" (type 0x04) 68# "rodirect" (type 0x05) 69# "scanner" (type 0x06) 70# "optical" (type 0x07) 71# "changer" (type 0x08) 72# "comm" (type 0x09) 73# "prepress1" (type 0x0A) 74# "prepress2" (type 0x0B) 75# "array_ctrl" (type 0x0C) 76# "ses" (type 0x0D) 77# "rbc" (type 0x0E) 78# "ocrw" (type 0x0F) 79# "bridge" (type 0x10) 80# "type_0x<typenum>" (types 0x11-0x1e are undefined by SCSI-3) 81# "type_unknown" (type 0x1f) 82# 83# In addition to binding to device types, sgen can be configured to bind to one 84# or more particular devices. The latter is accomplished by specifying the 85# Vendor and Product IDs returned by the device in response to the SCSI INQUIRY 86# command. This is accomplished by specifying pairs of Vendor ID and Product ID 87# strings in the inquiry-config-list property, below. "*" may be substituted 88# for the vendor ID as a wildcard. See sgen(7D) for details and extended usage 89# examples. 90# 91# USAGE EXAMPLE (sgen.conf) 92# 93# In this example, sgen is configured to bind to all scanner and ocrw devices in 94# the system, as well as the UltraToast 4000 from ACME, and the PowerToast 95# series of devices, regardless of vendor. 96# 97#device-type-config-list="scanner", "ocrw"; 98# 99#inquiry-config-list= "ACME", "UltraToast 4000", 100# "*", "PowerToast"; 101# 102# When using the sgen.conf method, after configuring the 103# device-type-config-list and/or the inquiry-config-list, the administrator 104# must uncomment those target/lun pairs at which there are devices for sgen to 105# control. If it is expected that devices controlled by sgen will be hotplugged 106# or added into the system later, it is recommended that all of the following 107# lines be uncommented. 108# 109#name="sgen" class="scsi" target=0 lun=0; 110#name="sgen" class="scsi" target=1 lun=0; 111#name="sgen" class="scsi" target=2 lun=0; 112#name="sgen" class="scsi" target=3 lun=0; 113#name="sgen" class="scsi" target=4 lun=0; 114#name="sgen" class="scsi" target=5 lun=0; 115#name="sgen" class="scsi" target=6 lun=0; 116#name="sgen" class="scsi" target=7 lun=0; 117#name="sgen" class="scsi" target=8 lun=0; 118#name="sgen" class="scsi" target=9 lun=0; 119#name="sgen" class="scsi" target=10 lun=0; 120#name="sgen" class="scsi" target=11 lun=0; 121#name="sgen" class="scsi" target=12 lun=0; 122#name="sgen" class="scsi" target=13 lun=0; 123#name="sgen" class="scsi" target=14 lun=0; 124#name="sgen" class="scsi" target=15 lun=0; 125 126