Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ieee1394(4) [xfree86 man page]

FIREWIRE(4)						   BSD Kernel Interfaces Manual 					       FIREWIRE(4)

NAME
firewire -- IEEE1394 High-performance Serial Bus SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device firewire Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): firewire_load="YES" DESCRIPTION
FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces. The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The firewire bus attaches to the controller. Additional drivers can be attached to the bus. Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address. FILES
/dev/fw0.0 /dev/fwmem0.0 SEE ALSO
fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8) HISTORY
The firewire driver first appeared in FreeBSD 5.0. AUTHORS
The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project. BUGS
See fwohci(4) for security notes. BSD
April 1, 2006 BSD

Check Out this Related Man Page

FWOHCI(4)						   BSD Kernel Interfaces Manual 						 FWOHCI(4)

NAME
fwohci -- OHCI FireWire chipset device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device firewire Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): firewire_load="YES" To disable physical access (see BUGS section for detail), put the following line in loader.conf(5): hw.firewire.phydma_enable=0 HARDWARE
The fwohci driver provides support for PCI/CardBus FireWire interface cards. The driver supports the following IEEE 1394 OHCI chipsets: o Adaptec AHA-894x/AIC-5800 o Apple Pangea o Apple UniNorth o Intel 82372FB o IOGEAR GUF320 o Lucent / Agere FW322/323 o NEC uPD72861 o NEC uPD72870 o NEC uPD72871/2 o NEC uPD72873 o NEC uPD72874 o National Semiconductor CS4210 o Ricoh R5C551 o Ricoh R5C552 o Sony CX3022 o Sony i.LINK (CXD3222) o Sun PCIO-2 (RIO 1394) o Texas Instruments PCI4410A o Texas Instruments PCI4450 o Texas Instruments PCI4451 o Texas Instruments TSB12LV22 o Texas Instruments TSB12LV23 o Texas Instruments TSB12LV26 o Texas Instruments TSB43AA22 o Texas Instruments TSB43AB21/A/AI/A-EP o Texas Instruments TSB43AB22/A o Texas Instruments TSB43AB23 o Texas Instruments TSB82AA2 o VIA Fire II (VT6306) SEE ALSO
firewire(4), fwe(4), fwip(4), sbp(4), fwcontrol(8), kldload(8) HISTORY
The fwohci device driver first appeared in FreeBSD 5.0. AUTHORS
The fwohci device driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa. BUGS
The driver allows physical access from any nodes on the bus by default. This means that any devices on the bus can read and modify any mem- ory space which can be accessed by an IEEE 1394 OHCI chip. It is allowed mostly for sbp(4) devices. This should be changed to allow it only for specific devices. Anyway, FireWire is a bus and not expected to be connected with un-trustable devices because a node can monitor all the traffic. BSD
March 3, 2008 BSD
Man Page

6 More Discussions You Might Find Interesting

1. Programming

make module for nic

Hello, Trying to solve a nic driver problem on RH linux with kernel 2.4.20-8. I seems that make it is looking in the place for the nic driver. Here is what I have tried and the result errors. Please ignore typos. modeprobe tulip /lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o:... (0 Replies)
Discussion started by: auji
0 Replies

2. UNIX for Dummies Questions & Answers

SoundCard.. Again

Hi everyone.I have an Audigy2 ZS sound card. I'm not a guru so don't send me faraway)) Well my card sounds only in front channels... can't setup 5.1. and i can't made a microphone works. PS: A have red this Yuriy Tsibizov (AKA chibis) many time. Here is some system info dmesg Copyright... (0 Replies)
Discussion started by: Levenson
0 Replies

3. Hardware

Wireless works, then dies requiring a reboot

Hello, I am having a problem with my wireless. Seems to be a relatively new problem over the past few weeks. I have an intel wireless. It seems like it can be fine for days, then in will quite working to the point a reboot is necessary. It may happen once and be fine, or may happen several times... (0 Replies)
Discussion started by: Narnie
0 Replies

4. IP Networking

my wireless usb adapter connect to net but the signal is very weak

i have wireless usb adapter rtl8187 from micromax company my proplem is the signal is very weak and i cannot open website can i increase the signal ? iwconfig lo no wireless extensions. eth0 no wireless extensions. wmaster0 no wireless extensions. wlan0... (5 Replies)
Discussion started by: rsd220
5 Replies

5. Shell Programming and Scripting

unix Library path variables.

Library path variables. I need to know the library rnvironment variable in linux. Ie, I install zlib directory in the custom path /usr/local/mylib and give --enable-zlib in the ffmpeg install, ffmpeg should check for the zlib libraries in the path /usr/local/mylib. Currently it checks /usr/lib... (5 Replies)
Discussion started by: anilcliff
5 Replies

6. Red Hat

insmod Error inserting `/lib/raid456.ko` -1 File Exist

hi every one , Wondering if any of you experienced this During "Centos5.6" Boot .. ! 1)NOT USING MMCONFIG 2)insmod Error inserting `/lib/raid456.ko` -1 File Exist Dell PowerEdge T110 with 4sata Controllers with Centos2.6.18-238.9.1.el5xen installed . /boot on /dev/md0 / on ... (18 Replies)
Discussion started by: Saed
18 Replies