Enable new Firewire stack in default kernel config
Bug #276463 reported by
Duncan Lithgow
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft | ||
Intrepid |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
An updated firewire stack and associate drivers has been merged into the mainline kernel for quite some time. This new stack fixes many design flaws present in the old stack.
Please also see the blueprint at https:/
description: | updated |
Changed in linux: | |
assignee: | apw → nobody |
status: | Invalid → Won't Fix |
Changed in linux: | |
assignee: | nobody → apw |
status: | Triaged → In Progress |
To post a comment you must log in.
Hi Duncan,
I assume you are referring to the CONFIG_FIREWIRE kernel config option. I'm pasting the Kconfig excerpt for the kernel team to reference when considering to enable this option:
comment "Enable only one of the two stacks, unless you know what you are doing"
depends on EXPERIMENTAL
config FIREWIRE ieee1394. wiki.kernel. org/index. php/Juju_ Migration
tristate "New FireWire stack, EXPERIMENTAL"
depends on EXPERIMENTAL
select CRC_ITU_T
help
This is the "Juju" FireWire stack, a new alternative implementation
designed for robustness and simplicity. You can build either this
stack, or the old stack (the ieee1394 driver, ohci1394 etc.) or both.
Please read http://
before you enable the new stack.
To compile this driver as a module, say M here: the module will be
called firewire-core.
This module functionally replaces ieee1394, raw1394, and video1394.
To access it from application programs, you generally need at least
libraw1394 version 2. IIDC/DCAM applications also need libdc1394
version 2. No libraries are required to access storage devices
through the firewire-sbp2 driver.