File:  [DragonFly] / src / share / man / man4 / fwohci.4
Revision 1.2: download - view: text, annotated - select for diffs
Tue Jun 17 04:36:59 2003 UTC (11 years, 3 months ago) by dillon
Branches: MAIN
CVS tags: HEAD
Add the DragonFly cvs id and perform general cleanups on cvs/rcs/sccs ids.  Most
ids have been removed from !lint sections and moved into comment sections.

    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: src/share/man/man4/fwohci.4,v 1.1.2.4 2003/03/03 18:51:16 trhodes Exp $
   33: .\" $DragonFly: src/share/man/man4/fwohci.4,v 1.2 2003/06/17 04:36:59 dillon Exp $
   34: .\"
   35: .\"
   36: .Dd April 10, 2000
   37: .Dt FWOHCI 4
   38: .Os
   39: .Sh NAME
   40: .Nm fwohci
   41: .Nd OHCI firewire chipset device driver
   42: .Sh SYNOPSIS
   43: .Cd "kldload firewire"
   44: .Pp
   45: or
   46: .Pp
   47: .Cd "device fwohci"
   48: .Cd "device firewire"
   49: .Sh DESCRIPTION
   50: The
   51: .Nm
   52: driver provides support for PCI/CardBus firewire interface cards.
   53: The driver supports following IEEE 1394 OHCI chipsets.
   54: .Pp
   55: .Bl -item
   56: .It
   57: NEC uPD72861
   58: .It
   59: Texas Instruments TSB12LV{22,23,26}, TSB43{AA22,AB22/A}, PCI44{10A,50}
   60: .It
   61: Sony CX3022
   62: .It
   63: VIA VT6306
   64: .It
   65: Ricoh R5C552
   66: .El
   67: .Sh SEE ALSO
   68: .Xr firewire 4 ,
   69: .Xr fwe 4 ,
   70: .Xr sbp 4 ,
   71: .Xr fwcontrol 8 ,
   72: .Xr kldload 8
   73: .Sh HISTORY
   74: The
   75: .Nm
   76: device driver first appeared in
   77: .Fx 5.0 .
   78: .Sh AUTHORS
   79: .An -nosplit
   80: The
   81: .Nm
   82: device driver was written by
   83: .An Katsushi Kobayashi
   84: and
   85: .An Hidetoshi Shimokawa .
   86: .Sh BUGS
   87: The driver allows physical access from any nodes on the bus by default.
   88: This means that any devices on the bus can read and modify any memory space
   89: which can be accessed by IEEE 1394 OHCI chip.
   90: It is allowed mostly for
   91: .Xr sbp 4
   92: devices.
   93: This should be changed to allow it only for specific devices.
   94: Anyway, FireWire is a bus and not expected to be connected with
   95: un-trustable devices because a node can monitor all the traffic.