Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel

[maximilian attems <max@stro.at>]

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.
 
> 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.

also lenny will "not" release with 2.6.22 nor 2.6.23,
2.6.23 superseeds 2.6.22 and for relevant testers out there
2.6.24-rc5 is available.

aboves page has direct links to userspace patches,
integrate them.

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)

the switch to juju allowed to close a nr of *longstanding* reports,
plus there is no known security problems unlike the old ieee1394
stack.
 
best regards

-- 
maks