According to http://ieee1394.wiki.kernel.org/index.php/Juju_Migration as of kernel 2.6.26 it is possible to build both stacks as modules provided one is properly blacklisted. Version 2 of libraw1394 would also be required to actually use the new stack.
This config would allow those inclined to test the new stack without compiling a custom kernel. I think v2 of libraw1394 could be installed parallel to v1 without impact.
From the above page:
"Regarding Linux 2.6.26, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. — Alternatively, build both stacks as modules but make sure that only one of them (the one you want) is being loaded. I.e. create proper blacklist entries in /etc/modprobe.conf; see below. Also, you need to upgrade your userland to libraw1394 v2 if you want to switch to the new drivers (or freely between old and new drivers)."
According to http:// ieee1394. wiki.kernel. org/index. php/Juju_ Migration as of kernel 2.6.26 it is possible to build both stacks as modules provided one is properly blacklisted. Version 2 of libraw1394 would also be required to actually use the new stack.
This config would allow those inclined to test the new stack without compiling a custom kernel. I think v2 of libraw1394 could be installed parallel to v1 without impact.
From the above page:
"Regarding Linux 2.6.26, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. — Alternatively, build both stacks as modules but make sure that only one of them (the one you want) is being loaded. I.e. create proper blacklist entries in /etc/modprobe.conf; see below. Also, you need to upgrade your userland to libraw1394 v2 if you want to switch to the new drivers (or freely between old and new drivers)."