On Sun, 2006-04-02 at 13:18 -0500, Gene Heskett wrote:
> Greetings;
>
> How much trouble will I have if I take the current 2.6.16.1 kernel src
> tree, nuke the ieee1394 directory of it, and bring the ieee1394
> directory in from the 2.6.12 tarball?
>
This has no chance of working.
> At 2.6.12, all the firewire stuff I needed to import from my camera,
> edit it, and make vcd's or dvd's out of it worked _flawlessly_. Now,
> at 2.6.16.1, and apparently since 2.6.13-rc1, kino is broken and must
> be killed by the system when it hangs. I figured it would get sorted,
> but apparently not.
>
That's always a bad assumption. Bugs should be reported early and
often.
> I can recover from backups all the stuff I've overwritten in the last 2
> days trying to make it work. That should make it all work again IF the
> ieee1394 stuff was reverted to the 2.6.12 version. Is this feasable at
> all?
>
No - it would be a much better use of your time to put together an
actionable bug report. The above is too vague... can you get an strace
or GDB backtrace of the hung process, dmesg, etc
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
