| fe.4 (84653) | fe.4 (84877) |
|---|---|
| 1.\" All Rights Reserved, Copyright (C) Fujitsu Limited 1995 2.\" 3.\" This document may be used, modified, copied, distributed, and sold, in 4.\" both source and printed form provided that the above copyright, these 5.\" terms and the following disclaimer are retained. The name of the author 6.\" and/or the contributor may not be used to endorse or promote products 7.\" derived from this software without specific prior written permission. 8.\" --- 7 unchanged lines hidden (view full) --- 16.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 17.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 18.\" OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF 19.\" SUCH DAMAGE. 20.\" 21.\" Contributed by M. Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>. 22.\" for fe driver. 23.\" | 1.\" All Rights Reserved, Copyright (C) Fujitsu Limited 1995 2.\" 3.\" This document may be used, modified, copied, distributed, and sold, in 4.\" both source and printed form provided that the above copyright, these 5.\" terms and the following disclaimer are retained. The name of the author 6.\" and/or the contributor may not be used to endorse or promote products 7.\" derived from this software without specific prior written permission. 8.\" --- 7 unchanged lines hidden (view full) --- 16.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 17.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 18.\" OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF 19.\" SUCH DAMAGE. 20.\" 21.\" Contributed by M. Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>. 22.\" for fe driver. 23.\" |
| 24.\" $FreeBSD: head/share/man/man4/man4.i386/fe.4 84653 2001-10-08 04:46:07Z murray $ | 24.\" $FreeBSD: head/share/man/man4/man4.i386/fe.4 84877 2001-10-13 09:08:37Z yokota $ |
| 25.Dd March 3, 1996 26.Dt FE 4 i386 27.Os 28.Sh NAME 29.Nm fe 30.Nd Fujitsu MB86960A/MB86965A based Ethernet adapters 31.Sh SYNOPSIS | 25.Dd March 3, 1996 26.Dt FE 4 i386 27.Os 28.Sh NAME 29.Nm fe 30.Nd Fujitsu MB86960A/MB86965A based Ethernet adapters 31.Sh SYNOPSIS |
| 32.Cd "device fe0 at isa? port 0x300 irq ?" | 32.Cd "device fe 1" 33.Pp 34In 35.Pa /boot/device.hints : 36.Cd hint.fe.0.at="isa" 37.Cd hint.fe.0.port="0x300" 38.Cd hint.fe.0.flags="0x0" |
| 33.Sh DESCRIPTION 34The 35.Nm 36is a network device driver 37for Ethernet adapters based on Fujitsu MB86960A, MB86965A, 38or other compatible chips. 39.Pp 40The driver provides automatic I/O port address configuration and 41automatic IRQ configuration, 42when used with suitable adapter hardware. 43.Pp 44The driver works with program I/O data transfer technique. 45It gives a fair performance. 46Shared memory is never used, even if the adapter has one. 47.Pp 48It currently works with Fujitsu FMV-180 series for ISA, 49Allied-Telesis AT1700 series and RE2000 series for ISA, 50and Fujitsu MBH10302 PC card. 51.Ss Parameters | 39.Sh DESCRIPTION 40The 41.Nm 42is a network device driver 43for Ethernet adapters based on Fujitsu MB86960A, MB86965A, 44or other compatible chips. 45.Pp 46The driver provides automatic I/O port address configuration and 47automatic IRQ configuration, 48when used with suitable adapter hardware. 49.Pp 50The driver works with program I/O data transfer technique. 51It gives a fair performance. 52Shared memory is never used, even if the adapter has one. 53.Pp 54It currently works with Fujitsu FMV-180 series for ISA, 55Allied-Telesis AT1700 series and RE2000 series for ISA, 56and Fujitsu MBH10302 PC card. 57.Ss Parameters |
| 52On the kernel configuration file, two parameters, | 58In the 59.Pa /boot/device.hints 60file, two parameters, |
| 53.Ar port 54and 55.Ar irq , 56must be specified to reflect adapter hardware settings. 57Another parameter 58.Ar flags 59can be specified to provide additional configuration as an option. | 61.Ar port 62and 63.Ar irq , 64must be specified to reflect adapter hardware settings. 65Another parameter 66.Ar flags 67can be specified to provide additional configuration as an option. |
| 60Other parameters of the device statement 61must appear as described on the synopsis. | |
| 62.Pp 63The 64.Ar port 65parameter specifies a base I/O port address of the adapter. 66It must match with the hardware setting of the adapter. 67The 68.Ar port | 68.Pp 69The 70.Ar port 71parameter specifies a base I/O port address of the adapter. 72It must match with the hardware setting of the adapter. 73The 74.Ar port |
| 69may be a left unspecified as 70.Dq Li \&? . | 75may be left unspecified by removing 76.Dl hint.fe.0.port="..." 77from the file. |
| 71In that case, the driver tries to detect the hardware setting 72of the I/O address automatically. 73This feature may not work with some adapter hardware. 74.Pp 75The 76.Ar irq 77parameter specifies an IRQ number used by the adapter. 78It must match the hardware setting of the adapter. 79.Ar Irq | 78In that case, the driver tries to detect the hardware setting 79of the I/O address automatically. 80This feature may not work with some adapter hardware. 81.Pp 82The 83.Ar irq 84parameter specifies an IRQ number used by the adapter. 85It must match the hardware setting of the adapter. 86.Ar Irq |
| 80may be left unspecified as 81.Dq Li \&? ; | 87may be left unspecified by removing 88.Dl hint.fe.0.irq="..." 89from the file. |
| 82in that case, the driver tries to detect 83the hardware setting of the IRQ automatically. 84This feature may not work on some adapters. 85.Pp 86The 87.Ar flags 88is a numeric value which consists of a combination of various device settings. 89The following flags are defined in the current version. --- 92 unchanged lines hidden (view full) --- 182Both automatic IRQ detection and automatic I/O port address detection 183is available with these adapters. 184.Pp 185Automatic I/O port address detection feature of 186.Nm 187works mostly fine for FMV-180 series. 188It works even if there are two or more FMV-180s in a system. 189However, some combination of other adapters may confuse the driver. | 90in that case, the driver tries to detect 91the hardware setting of the IRQ automatically. 92This feature may not work on some adapters. 93.Pp 94The 95.Ar flags 96is a numeric value which consists of a combination of various device settings. 97The following flags are defined in the current version. --- 92 unchanged lines hidden (view full) --- 190Both automatic IRQ detection and automatic I/O port address detection 191is available with these adapters. 192.Pp 193Automatic I/O port address detection feature of 194.Nm 195works mostly fine for FMV-180 series. 196It works even if there are two or more FMV-180s in a system. 197However, some combination of other adapters may confuse the driver. |
| 190It is recommended not to use 191.Em "port ?" | 198It is recommended to explicitly specify 199.Ar port |
| 192when you experience some difficulties with hardware probe. 193.Pp 194Automatic IRQ detection feature of 195.Nm 196works reliably for FMV-180 series. | 200when you experience some difficulties with hardware probe. 201.Pp 202Automatic IRQ detection feature of 203.Nm 204works reliably for FMV-180 series. |
| 197It is recommended to use 198.Em "irq ?" | 205It is recommended to explicitly specify 206.Ar irq |
| 199always for FMV-180. 200The hardware setting of IRQ is read 201from the configuration EEPROM on the adapter, 202even when the kernel config file specifies an IRQ value. 203The driver will generate a warning message, | 207always for FMV-180. 208The hardware setting of IRQ is read 209from the configuration EEPROM on the adapter, 210even when the kernel config file specifies an IRQ value. 211The driver will generate a warning message, |
| 204if the IRQ setting specified in the kernel config file | 212if the IRQ setting specified in 213.Pa /boot/device.hints |
| 205does not match one stored in EEPROM. | 214does not match one stored in EEPROM. |
| 206Then, it will use the value specified in the config file. | 215Then, it will use the value specified in the file. |
| 207(This behavior has been changed from the previous releases.) 208.Ss Allied-Telesis AT1700 series and RE2000 series adapters 209Automatic I/O port address detection 210is available with Allied-Telesis AT1700 series and RE2000 series, 211while it is less reliable than FMV-180 series. 212Using the feature with Allied-Telesis adapters 213is not recommended. 214.Pp 215Automatic IRQ detection is also available with some limitation. 216The 217.Nm 218driver 219tries to get IRQ setting from the configuration EEPROM on the board, 220if | 216(This behavior has been changed from the previous releases.) 217.Ss Allied-Telesis AT1700 series and RE2000 series adapters 218Automatic I/O port address detection 219is available with Allied-Telesis AT1700 series and RE2000 series, 220while it is less reliable than FMV-180 series. 221Using the feature with Allied-Telesis adapters 222is not recommended. 223.Pp 224Automatic IRQ detection is also available with some limitation. 225The 226.Nm 227driver 228tries to get IRQ setting from the configuration EEPROM on the board, 229if |
| 221.Dq irq ?\& 222is specified in the configuration file. | 230.Ar irq 231is not specified in 232.Pa /boot/device.hints . |
| 223Unfortunately, 224AT1700 series and RE2000 series seems to have two types of models; 225One type allows IRQ selection from 3/4/5/9, 226while the other from 10/11/12/15. 227Identification of the models are not well known. 228Hence, automatic IRQ detection with Allied-Telesis adapters 229may not be reliable. 230Specify an exact IRQ number if any troubles are encountered. --- 79 unchanged lines hidden --- | 233Unfortunately, 234AT1700 series and RE2000 series seems to have two types of models; 235One type allows IRQ selection from 3/4/5/9, 236while the other from 10/11/12/15. 237Identification of the models are not well known. 238Hence, automatic IRQ detection with Allied-Telesis adapters 239may not be reliable. 240Specify an exact IRQ number if any troubles are encountered. --- 79 unchanged lines hidden --- |