| fwohci.4 (f5bff4606924f7bfd322e93578cf5103cb362b2e) | fwohci.4 (ace5be682d8e04a1dccf8939efa1babe059e3609) |
|---|---|
| 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. --- 51 unchanged lines hidden (view full) --- 60Sony CX3022 61.It 62VIA VT6306 63.It 64Ricoh R5C552 65.El 66.Sh SEE ALSO 67.Xr firewire 4 , | 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. --- 51 unchanged lines hidden (view full) --- 60Sony CX3022 61.It 62VIA VT6306 63.It 64Ricoh R5C552 65.El 66.Sh SEE ALSO 67.Xr firewire 4 , |
| 68.Xr fwcontrol 8 , | |
| 69.Xr fwe 4 , | 68.Xr fwe 4 , |
| 70.Xr kldload 8 , 71.Xr sbp 4 | 69.Xr sbp 4 , 70.Xr fwcontrol 8 , 71.Xr kldload 8 |
| 72.Sh HISTORY 73The 74.Nm 75device driver first appeared in 76.Fx 5.0 . 77.Sh AUTHORS | 72.Sh HISTORY 73The 74.Nm 75device driver first appeared in 76.Fx 5.0 . 77.Sh AUTHORS |
| 78.An -nosplit |
|
| 78The 79.Nm 80device driver was written by 81.An Katsushi Kobayashi 82and 83.An Hidetoshi Shimokawa . | 79The 80.Nm 81device driver was written by 82.An Katsushi Kobayashi 83and 84.An Hidetoshi Shimokawa . |
| 84.Pp | |
| 85.Sh BUGS 86The driver allows physical access from any nodes on the bus by default. 87This means that any devices on the bus can read and modify any memory space | 85.Sh BUGS 86The driver allows physical access from any nodes on the bus by default. 87This means that any devices on the bus can read and modify any memory space |
| 88which can be accessed by IEEE 1394 OHCI chip. It is allowed mostly 89for sbp(4) devices. This should be changed to allow it only for specific 90devices. Anyway FireWire is a bus and not expected to be connected with 91un-trustable devices because a node can monitor all the traffic. | 88which can be accessed by IEEE 1394 OHCI chip. 89It is allowed mostly for 90.Xr sbp 4 91devices. 92This should be changed to allow it only for specific devices. 93Anyway, FireWire is a bus and not expected to be connected with 94un-trustable devices because a node can monitor all the traffic. |