On Wed, Mar 25, 2009 at 12:37:37PM +0100, Grammostola Rosea wrote: > > >> Why only in 64studio and not in plain Debian? > > What's good for Debian is good for us :-) but the Debian project may > > not want to tweak the kernel or the FireWire stack just for the > > benefit of FFADO users. In the 64 Studio project we have more > > flexibility to do things like that. > > Some background info here: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276463 > What is true about this? Shouldn't plain Debian also support those Pro > audio Firewire devices, the ones the FFADO team are making drivers for?
It's easy: http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Module_auto-loading Compile both modules and blacklist the new Juju modules. That's the current upstream recommendation. Even if the default will change around 2.6.30 (or later, I don't know the exact schedule), the FFADO users could still enable the old ieee1394 modules. We already have libraw1394-v2 in sid, but as outlined, FFADO currently only works with the old stack. This might also change in the future, especially if the Google Summer of Code project succeeds. (in-kernel alsa driver module for firewire audio) IOW: ship both stacks, decide for one and blacklist the other. FFADO users will then select the appropriate one. And of course, I'll continue looking into the FFADO-on-Juju issue. HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
