On Thu, Dec 13, 2007 at 10:27:40AM +0100, maximilian attems wrote: > On Wed, Dec 12, 2007 at 11:17:28PM -0600, Steve M. Robbins wrote: > > > > As noted by Guus Sliepen, switching from a functioning driver to an > > experimental driver with no library support is not going to cause the > > latter to be improved. It's simply annoying to the user. > > that is a pretty bold incompetent statement, > for all relevant libraries patches exists. > take them out of the corresponding git repos. By "user", I meant "Debian user". There is manifestly no library support for the Debian user. Git repos are not relevant here. > > The linux1394.org people say: > > > > At the time of this writing (12/2007), there are still multiple > > problems with the new FireWire kernel driver stack (alias Juju) > > compared to the old stack [...] > > > > Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux > > distributors (kernel packagers) as well as to regular users is: Build > > only the old IEEE 1394 drivers. > > > > http://wiki.linux1394.org/JujuMigration > > et ceterum censo aboves quote is from 1 of the 2 maintainers. > the other maintainer considered it fit enough for fedora stable > release 7 and 8. And the Fedora users are complaining as well. I cannot see how you think it improves things to produce a system (Debian Sid) with an unusable 1394 subsystem. It is clearly not being tested nor improved, since anyone who wants to use it is rebuilding the kernel with the old drivers again! > the new stack has many advantages: > - leaner codebase (less than 8k lines of code compared to 30k lines of > code in the old stack) > - cleaned-up and improved in-stack APIs > (with the side effect of getting rid of a bunch of old bugs) > - design (no kernel threads, compared to one subsystem thread and one > thread per FireWire controller in the old stack) Those are all great theoretical advantages. None of them matter to me, as a user. What matters is a working system. And Debian is -- allegedly -- about the users. In that light, I would think that the best approach is: 1. Make sure all libraries are patched. 2. Switch the kernel module. Rather than the other way around. Best regards, -Steve
Attachment:
signature.asc
Description: Digital signature