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######################################################################### 22# 23# Copyright 2008 Sun Microsystems, Inc. All rights reserved. 24# Use is subject to license terms. 25# 26# Driver.conf file for the BGE driver, for 27# Broadcom 579x Gigabit Ethernet devices 28# 29# All the properties below can be set globally (i.e. for all instances 30# of BGE), or on a per-instance basis. See driver.conf(4) for details 31# of the syntax of global and per-instance properties. 32# 33# Properties specified in this file take effect when the driver is first 34# loaded, typically just after system boot. Changes to the file will 35# therefore not take effect until the next reboot, but will be permanent 36# thereafter. 37# 38# Some of the driver's parameters can also be changed using ndd(1m). 39# Changes made with ndd apply only to a specific instance (e.g. bge1). 40# They take effect immediately, but are lost if the driver is unloaded. 41# 42######################################################################### 43# 44# The autonegotiation feature can be controlled by the boolean properties 45# listed below. 46# 47# Firstly, 'adv_autoneg_cap' controls whether autonegotiation is enabled. 48# 49# If autonegotiation is turned OFF ("forced mode"), the remaining 'adv_*' 50# speed/duplex properties force selection of a specific mode, namely, 51# the first mode found to be enabled, in highest-to-lowest speed order 52# (thus, if adv_1000fdx_cap=1, all other values will be ignored; to force 53# 10/hdx mode, *all* the faster modes must be explicitly disabled). 54# 55# BEWARE - it's very easy to end up with a non-working link using forced 56# mode. There's NO validation that the link partner actually supports 57# the mode that this device has been forced into. In some cases, this 58# will prevent the link coming up; in others, the link status will show 59# 'up' (electrical connection made) but data transfer will not work at 60# all, or will work poorly (low throughput, high collision rates, etc). 61# 62# Note that many switches *require* autonegotiation in order to operate 63# at 1000Mbps or in full-duplex mode or with flow control. In other words, 64# the only combinations that are likely to work with autonegotiation off 65# are 100Mbps/half-duplex and 10Mbps/half-duplex, unless the peer has also 66# been manually forced to some other (matching) combination. 67# 68# With autonegotiation ON (the default and preferred mode), the 'adv_*' 69# properties control which capabilities are advertised to the partner. 70# The default is to advertise all the capabilities that the hardware 71# supports; thus, the properties below serve only to limit the advertised 72# capabilities to restricted subset -- it is not possible to advertise a 73# capability that the hardware does not support. 74# 75# The autonegotiation process will then automagically select the fastest 76# speed/duplex mode and greatest degree of flow control supported by both 77# partners. 78# 79# If the local device is set to autonegotiate, but the link partner can't 80# or doesn't autonegotiate, the correct speed will be determined anyway, 81# and HALF-DUPLEX mode will be selected, as mandated by the IEEE802.3 82# standard. This will yield the correct result if the partner is in fact 83# incapable of autonegotiating: it must be a half-duplex device, because 84# the only devices that don't support autonegotation are half-duplex (the 85# standard says that all full-duplex-capable devices must also support 86# autonegotiation). 87# 88# However, this choice will NOT be correct if the peer is actually capable 89# of autonegotiation and full-duplex operation, and has been manually set 90# to "forced full-duplex without autonegotiation" (a mode not recommended 91# by the IEEE standard). The link will appear to work, but the duplex 92# mismatch will result in packet loss and spurious "late collisions". In 93# such cases, the preferred solution is to enable autonegotiation by the 94# peer. Failing that, autonegotiation by the BGE device can be disabled, 95# and forced mode used to match the peer's forced settings as above. 96# 97# adv_autoneg_cap = 1; 98# adv_1000fdx_cap = 1; 99# adv_1000hdx_cap = 1; 100# adv_100T4_cap = 0; 101# adv_100fdx_cap = 1; 102# adv_100hdx_cap = 1; 103# adv_10fdx_cap = 1; 104# adv_10hdx_cap = 1; 105# adv_asym_pause_cap = 0; 106# adv_pause_cap = 0; 107# 108# All of these parameters can can also be queried and modified at run-time 109# by use of the ndd(1m) command. 110# 111######################################################################### 112# 113# OBP's device driver exports methods to set the link speed explicity, 114# which then pass the information to the Solaris driver through the 115# 'transfer-speed' property. It therefore SHOULDN'T be set here, but 116# is documented for completeness. If the 'transfer-speed' property is 117# set to 10, 100, or 1000, the link will be set to the selected speed, 118# and autonegotiation ENABLED but restricted to the specified speed. 119# The correct duplex setting will be determined by autonegotiation. 120# 121# This property, if set, overrides and alters the settings of the adv_* 122# parameters corresponding to the properties above. 123# 124# transfer-speed = 1000; 125# 126######################################################################### 127# 128# As a third alternative, the following two properties can be set to 129# force the link speed/duplex setting instead. Doing so will override 130# and alter the settings of the adv_* parameters corresponding to the 131# properties above, and take precedence over all other means of setting 132# the speed/duplex at boot time. 133# 134# Autonegotiation will be DISABLED if EITHER of these properties is set, 135# therefore BOTH properties should be set explicity if either one is. 136# 'speed' may be set to 10, 100 or 1000, while 'full-duplex' may be 0 or 1. 137# 138# See the warning above about the potential for misconfiguration when 139# autonegotiation is disabled. Defining these properties could leave your 140# system configured so that the network will not work at all after reboot, 141# requiring manual intervention and further reboots to recover! 142# 143# speed = 100; 144# full-duplex = 0; 145# 146######################################################################### 147# 148# The property below represents the list of subsystem vendor/device pairs 149# with which driver operation is supported. This list will be updated and 150# extended as new subsystems are validated ... 151# 152bge-known-subsystems = 0x108e1647, 153 0x108e1648, 154 0x108e16a7, 155 0x108e16a8, 156 0x17c20010, 157 0x17341013, 158 0x101402a6, 159 0x10f12885, 160 0x17c20020, 161 0x10b71006, 162 0x10280109, 163 0x102801f8, 164 0x1028865d, 165 0x0e11005a, 166 0x0e1100cb, 167 0x103c12bc; 168######################################################################### 169# 170# The properties below represents the number of receive and send ring used. 171# For BCM5705, BCM5782, etc, there are only 1 receive ring and 1 send ring. 172# Otherwise, there can be up to 16 receive rings and 4 send rings. 173# 174bge-rx-rings = 16; 175bge-tx-rings = 1; 176 177