CONFIG_FIREWIRE_OHCI: OHCI-1394 controllers

General informations

The Linux kernel configuration item CONFIG_FIREWIRE_OHCI has multiple definitions:

OHCI-1394 controllers found in drivers/firewire/Kconfig

The configuration item CONFIG_FIREWIRE_OHCI:

• prompt: OHCI-1394 controllers
• type: tristate
• depends on: CONFIG_PCI && CONFIG_FIREWIRE && CONFIG_MMU
• defined in drivers/firewire/Kconfig
• found in Linux kernels: 2.6.26–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD
• modules built: firewire-ohci

Help text

Enable this driver if you have a FireWire controller based on the OHCI specification. For all practical purposes, this is the only chipset in use, so say Y here.

To compile this driver as a module, say M here: The module will be called firewire-ohci.

Support for OHCI FireWire host controllers found in drivers/firewire/Kconfig

The configuration item CONFIG_FIREWIRE_OHCI:

• prompt: Support for OHCI FireWire host controllers
• type: tristate
• depends on: CONFIG_PCI && CONFIG_FIREWIRE
• defined in drivers/firewire/Kconfig
• found in Linux kernels: 2.6.22–2.6.25
• modules built: firewire-ohci

Help text

Enable this driver if you have a FireWire controller based on the OHCI specification. For all practical purposes, this is the only chipset in use, so say Y here.

To compile this driver as a module, say M here: The module will be called firewire-ohci. It replaces ohci1394 of the classic IEEE 1394 stack.

NOTE:

You should only build ohci1394 or firewire-ohci, but not both. If you nevertheless want to install both, you should configure them only as modules and blacklist the driver(s) which you don't want to have auto-loaded. Add either

blacklist firewire-ohci or blacklist ohci1394 blacklist video1394 blacklist dv1394

to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf depending on your distribution. The latter two modules should be blacklisted together with ohci1394 because they depend on ohci1394.

If you have an old modprobe which doesn't implement the blacklist directive, use "install modulename /bin/true" for the modules to be blacklisted.

Hardware

PCI

Numeric ID (from LKDDb) and names (from pci.ids) of recognized devices:

• class: 0c ("Serial bus controller"), subclass: 00 ("FireWire (IEEE 1394)"), prog-if: 10 ("OHCI")
• class: 0c ("Serial bus controller"), subclass: 00 ("FireWire (IEEE 1394)"), prog-if: 10 ("OHCI")
• class: 0c ("Serial bus controller"), subclass: 00 ("FireWire (IEEE 1394)"), prog-if: 10 ("OHCI")

LKDDb

Raw data from LKDDb:

• lkddb module firewire-ohci CONFIG_FIREWIRE_OHCI : drivers/firewire/Kconfig : "OHCI-1394 controllers" # in 2.6.22–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD
• lkddb pci .... .... .... .... 0c0010 : CONFIG_FIREWIRE CONFIG_FIREWIRE_OHCI : drivers/firewire/fw-ohci.c # in 2.6.22–2.6.30
• lkddb pci .... .... .... .... 0c0010 : CONFIG_FIREWIRE CONFIG_FIREWIRE_OHCI : drivers/firewire/ohci.c # in 2.6.31–2.6.35
• lkddb pci .... .... .... .... 0c0010 : CONFIG_FIREWIRE_OHCI : drivers/firewire/ohci.c # in 2.6.36–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)
• The Linux PCI ID Repository.

Automatic links from Google (and ads)

Custom Search

Popular queries: