Bug#539024: marked as done (linux-2.6: Please enable both firewire stacks, ieee1394 and Juju)
Your message dated Tue, 28 Jul 2009 17:55:59 +0200
with message-id <20090728155559.GI16147@baikonur.stro.at>
and subject line Re: Bug#539024: linux-2.6: Please enable both firewire stacks, ieee1394 and Juju
has caused the Debian Bug report #539024,
regarding linux-2.6: Please enable both firewire stacks, ieee1394 and Juju
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
539024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539024
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: normal
Hi!
At least 2.6.30-2 ships with the new firewire stack (Juju). This stack
is nearing feature-completion, however, there's at least one exception:
FFADO, the userland driver for firewire audio cards, can only be used
with the old stack.
This is a known problem, it's mentioned in the 1394wiki:
http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Compatibility_and_stability
There's also an FFADO ticket about it:
http://subversion.ffado.org/ticket/78
We now have the case that FFADO has entered Debian Unstable, but the
kernel isn't capable of running it. ;)
I guess this is somewhat related to #435062. Though the versions don't
match, but the bugs could probably be merged.
There's a Google Summer of Code project trying to write an in-kernel
driver for firewire audio, but currently, there are no results. It would
take some months to complete it.
Long story short: can you enable both stacks? I guess blacklisting the
old stack would be ok, it's mentioned here:
http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Module_auto-loading
I don't know if debconf is acceptable for a kernel package, so it could
ask which stack to use and create /etc/modprobe.d/ according to the
user's reply.
I could also tweak such a file in the FFADO package, so the kernel can
default to the new stack, and only the presence of FFADO enables the old
stack after informing the user.
TIA,
Cheerio
--- End Message ---
--- Begin Message ---
On Tue, Jul 28, 2009 at 05:13:36PM +0200, Adrian Knoth wrote:
> Package: linux-2.6
> Severity: normal
at most wishlist, but that question has already been answered.
> Hi!
>
> At least 2.6.30-2 ships with the new firewire stack (Juju). This stack
> is nearing feature-completion, however, there's at least one exception:
> FFADO, the userland driver for firewire audio cards, can only be used
> with the old stack.
the new stack will catch up, we shipped it even although
it shortcomings in 2.6.24 were bigger.
> This is a known problem, it's mentioned in the 1394wiki:
>
> http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Compatibility_and_stability
>
> There's also an FFADO ticket about it:
>
> http://subversion.ffado.org/ticket/78
>
>
> We now have the case that FFADO has entered Debian Unstable, but the
> kernel isn't capable of running it. ;)
>
> I guess this is somewhat related to #435062. Though the versions don't
> match, but the bugs could probably be merged.
>
> There's a Google Summer of Code project trying to write an in-kernel
> driver for firewire audio, but currently, there are no results. It would
> take some months to complete it.
>
>
> Long story short: can you enable both stacks? I guess blacklisting the
> old stack would be ok, it's mentioned here:
>
> http://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Module_auto-loading
>
>
> I don't know if debconf is acceptable for a kernel package, so it could
> ask which stack to use and create /etc/modprobe.d/ according to the
> user's reply.
>
> I could also tweak such a file in the FFADO package, so the kernel can
> default to the new stack, and only the presence of FFADO enables the old
> stack after informing the user.
we have no mechanism for blacklisting. FFADO needs to catch up to the
new firewire stack.
for squeeze we will not enable the older stack also we won't shipp with
2.6.30 but with much newer linux-2.6.
--- End Message ---
Reply to: