Re: Bug#436267: Firewire support in lenny
On Tue, Feb 12, 2008 at 11:27:29AM +0100, Guus Sliepen wrote:
> On Sun, Feb 03, 2008 at 10:04:18AM +0100, Marc 'HE' Brockschmidt wrote:
> > Early March 2008
> > Very soft freeze
> > Mid of July 2008
> > Full freeze
> I guess that means that lenny will be released with linux kernel
> 2.6.24.x. If that is so, then I kindly request that the debian kernel
> packages will be released with the stable Firewire stack modules
no certainly not, we haven't yet discussed the release kernel.
options are 2.6.25 or 2.6.26.
> The current kernel package mainainer(s) has (have) decided to disable
> the stable modules in favour of the new and experimental JuJu stack.
> The new stack has the advantage that is more secure and has a cleaner
> code base, but the drawback that a lot of devices and features are not
> yet supported. To summarise what the JuJu developers themselves say
> about the current state of the new stack:
[snipp http://wiki.linux1394.org/JujuMigration ]
> Regarding Linux 2.6.22...2.6.24, the best advice to Linux distributors
> (kernel packagers) as well as to regular users is: Build only the old
> IEEE 1394 drivers.
you omit the interesting next paragraph:
"Building the new drivers is only for advanced users (who for example
want the better speed of firewire-sbp2 relative to sbp2) - and for
distributors who know what is required in userspace to make use of the
new drivers and who can get bugfixes backported and rolled out quickly."
on the kernel side we do backport firewire patches.
for the userspace side i still see lack of action on libdc1394
"2008/01/05: The official version 2.0.0 has been released.
2008/01/05: A first set of fixes have been released (version 2.0.1)"
why is that not even in unstable/experimental?
> users it is better to load the modules for the JuJu stack by default.
> But for those people who need the stable stack to do work, the modules
> for the stable stack should be available. There is no reason not to
> build both stacks, they don't conflict with each other (except that only
> one works if you load both, of course).
> I hope the kernel package maintainer(s) will make sure kernel packages
> with the stable modules available, but blacklisted by default, will
> enter testing soon, so that users of testing get a chance to test it
> before lenny is released.
the progress of the juju stack is very nice, there are quite some
fixes queued for 2.6.25, we will make those snapshots available
if the regression list for 2.6.25 is still high we may reconsider
there to build the old stack with blacklisted modules.
that has always been our stated fallback position, currently in the
development phase we encourage testing of the newer stack
on latest linux-images.
>  http://bugs.debian.org/436267
>  http://wiki.linux1394.org/JujuMigration
>  http://en.wikipedia.org/wiki/FireWire#Security_issues