1.\" Copyright (c) 1998,1999,2000 Katsushi Kobayashi and Hidetoshi Shimokawa 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the acknowledgement as bellow: 14.\" 15.\" This product includes software developed by K. Kobayashi and H. Shimokawa 16.\" 17.\" 4. The name of the author may not be used to endorse or promote products 18.\" derived from this software without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 21.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 22.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 23.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, 24.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 25.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 26.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 28.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 29.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 30.\" POSSIBILITY OF SUCH DAMAGE. 31.\" 32.\" $FreeBSD$ 33.\" 34.\" 35.Dd June 23, 2005 36.Dt FWOHCI 4 37.Os 38.Sh NAME 39.Nm fwohci 40.Nd OHCI FireWire chipset device driver 41.Sh SYNOPSIS 42To compile this driver into the kernel, 43place the following line in your 44kernel configuration file: 45.Bd -ragged -offset indent 46.Cd "device firewire" 47.Ed 48.Pp 49Alternatively, to load the driver as a 50module at boot time, place the following line in 51.Xr loader.conf 5 : 52.Bd -literal -offset indent 53firewire_load="YES" 54.Ed 55.Sh HARDWARE 56The 57.Nm 58driver provides support for PCI/CardBus FireWire interface cards. 59The driver supports the following IEEE 1394 OHCI chipsets: 60.Pp 61.Bl -bullet -compact 62.It 63Adaptec AHA-894x/AIC-5800 64.It 65Apple Pangea 66.It 67Apple UniNorth 68.It 69Intel 82372FB 70.It 71IOGEAR GUF320 72.It 73Lucent / Agere FW322/323 74.It 75NEC uPD72861 76.It 77NEC uPD72870 78.It 79NEC uPD72871/2 80.It 81NEC uPD72873 82.It 83NEC uPD72874 84.It 85National Semiconductor CS4210 86.It 87Ricoh R5C551 88.It 89Ricoh R5C552 90.It 91Sony CX3022 92.It 93Sony i.LINK (CXD1947) 94.It 95Sony i.LINK (CXD3222) 96.It 97Sun PCIO-2 (RIO 1394) 98.It 99Texas Instruments PCI4410A 100.It 101Texas Instruments PCI4450 102.It 103Texas Instruments PCI4451 104.It 105Texas Instruments TSB12LV22 106.It 107Texas Instruments TSB12LV23 108.It 109Texas Instruments TSB12LV26 110.It 111Texas Instruments TSB43AA22 112.It 113Texas Instruments TSB43AB21/A/AI/A-EP 114.It 115Texas Instruments TSB43AB22/A 116.It 117Texas Instruments TSB43AB23 118.It 119Texas Instruments TSB82AA2 120.It 121VIA Fire II (VT6306) 122.El 123.Sh SEE ALSO 124.Xr firewire 4 , 125.Xr fwe 4 , 126.Xr fwip 4 , 127.Xr sbp 4 , 128.Xr fwcontrol 8 , 129.Xr kldload 8 130.Sh HISTORY 131The 132.Nm 133device driver first appeared in 134.Fx 5.0 . 135.Sh AUTHORS 136.An -nosplit 137The 138.Nm 139device driver was written by 140.An Katsushi Kobayashi 141and 142.An Hidetoshi Shimokawa . 143.Sh BUGS 144The driver allows physical access from any nodes on the bus by default. 145This means that any devices on the bus can read and modify any memory space 146which can be accessed by an IEEE 1394 OHCI chip. 147It is allowed mostly for 148.Xr sbp 4 149devices. 150This should be changed to allow it only for specific devices. 151Anyway, FireWire is a bus and not expected to be connected with 152un-trustable devices because a node can monitor all the traffic. 153