Your message dated Wed, 06 Jan 2010 04:24:57 +0000
with message-id <1262751897.2377.16.ca...@localhost>
and subject line Re: Alternative (buggy, incomplete) firewire stack shipped
instead of the stable one
has caused the Debian Bug report #449272,
regarding Alternative (buggy, incomplete) firewire stack shipped instead of the
stable one
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 [email protected]
immediately.)
--
449272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449272
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.22-3-686
Version: 2.6.22-5
Severity: important
Debian choose to ship the alternative firewire stack on recent kernels.
Firewire maintainers are not recommending this (see
http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack
is incomplete. For instance, I can't do ethernet over firewire with 2.6.22,
I have to go back to 2.6.18, which gives me other kind of trouble.
-- Package-specific info:
** Version:
Linux version 2.6.22-3-686 (Debian 2.6.22-5) ([email protected]) (gcc version
4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Oct 22 22:11:56
UTC 2007
--- End Message ---
--- Begin Message ---
DV capture works for me using the test program included in
<http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;bug=545112>.
Therefore I believe that kino is at fault, not the kernel.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real world is often a special case.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
