mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Firewire problems, apparently since 2.6.13-rc1
Date: Sun, 02 Apr 2006 13:18:16 -0500	[thread overview]
Message-ID: <200604021418.16263.gene.heskett@verizon.net> (raw)

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?

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.

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?

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

             reply	other threads:[~2006-04-02 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02 18:18 Gene Heskett [this message]
2006-04-02 19:00 ` Lee Revell
2006-04-02 20:25   ` Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200604021418.16263.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=gene.heskett@verizononline.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®