From: Ben Collins <bcollins@debian.org>
To: gaxt <gaxt@rogers.com>, Torrey Hoffman <thoffman@arnor.net>,
Sam Bromley <sbromley@cogeco.ca>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux firewire devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Firewire
Date: Sat, 26 Jul 2003 13:45:37 -0400 [thread overview]
Message-ID: <20030726174537.GF490@phunnypharm.org> (raw)
In-Reply-To: <20030726165259.GV23196@ruvolo.net>
On Sat, Jul 26, 2003 at 09:52:59AM -0700, Chris Ruvolo wrote:
> On Fri, Jul 25, 2003 at 04:11:29PM -0400, Ben Collins wrote:
> > Kick ass. I've commited this change to the 1394 repo. Linus will get the
> > fix soon. I'll also send it to Marcelo for 2.4.22.
> >
> > Please, if you are testing, use the code at www.linux1394.org's viewcvs
> > (trunk tarball will replace drivers/ieee1394 in 2.6, branches/linux-2.4
> > will do the same for 2.4).
>
> Its all working! Compiled the 1014 rev, and everything looks good. dvgrab,
> kino, gscanbus, even GnomeMeeting 0.98 with /dev/video1394.
>
> Thanks for all your help, and the time spent tracking down this problem!
Thanks for the feedback. I'm glad this is finally fixed.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
next prev parent reply other threads:[~2003-07-26 17:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 13:34 Firewire gaxt
2003-07-24 22:35 ` Firewire Chris Ruvolo
2003-07-24 22:36 ` Firewire Ben Collins
2003-07-24 23:09 ` Firewire Chris Ruvolo
2003-07-24 23:14 ` Firewire Ben Collins
2003-07-24 23:48 ` Firewire Chris Ruvolo
2003-07-24 23:45 ` Firewire Ben Collins
2003-07-25 0:07 ` Firewire Chris Ruvolo
2003-07-25 0:14 ` Firewire Chris Ruvolo
2003-07-25 1:13 ` Firewire Torrey Hoffman
2003-07-25 1:27 ` Firewire Chris Ruvolo
2003-07-25 1:29 ` Firewire Ben Collins
2003-07-25 2:00 ` Firewire Chris Ruvolo
2003-07-25 2:19 ` Firewire Ben Collins
2003-07-25 3:23 ` Firewire Sam Bromley
2003-07-25 4:12 ` Firewire Ben Collins
2003-07-25 5:39 ` Firewire Chris Ruvolo
2003-07-25 13:34 ` Firewire Ben Collins
2003-07-25 14:06 ` Firewire gaxt
2003-07-25 13:47 ` Firewire Ben Collins
2003-07-25 14:23 ` Firewire gaxt
2003-07-25 15:28 ` Firewire gaxt
2003-07-25 14:29 ` Firewire Chris Ruvolo
2003-07-25 14:29 ` Firewire Ben Collins
2003-07-25 15:40 ` Firewire Ben Collins
2003-07-25 16:07 ` Firewire Chris Ruvolo
2003-07-25 16:18 ` Firewire Ben Collins
2003-07-25 17:02 ` Firewire Chris Ruvolo
2003-07-25 17:07 ` Firewire Ben Collins
2003-07-25 17:51 ` Firewire Torrey Hoffman
2003-07-25 18:13 ` Firewire Chris Ruvolo
2003-07-25 18:12 ` Firewire Ben Collins
2003-07-25 18:43 ` Firewire gaxt
2003-07-25 18:26 ` Firewire Ben Collins
2003-07-25 18:45 ` Firewire Ben Collins
2003-07-25 19:16 ` Firewire gaxt
2003-07-25 19:35 ` Firewire Chris Ruvolo
2003-07-25 20:11 ` Firewire Ben Collins
2003-07-25 21:48 ` Firewire gaxt
2003-07-26 4:41 ` Firewire (One fix worked, now getting oops) Sam Bromley
2003-07-26 15:12 ` Ben Collins
2003-07-26 17:41 ` Sam Bromley
2003-07-26 17:45 ` Ben Collins
2003-07-26 16:52 ` Firewire Chris Ruvolo
2003-07-26 17:45 ` Ben Collins [this message]
2003-07-25 20:48 ` Firewire Torrey Hoffman
2003-07-25 20:44 ` Firewire Ben Collins
2003-07-25 18:18 ` Firewire Torrey Hoffman
2003-07-25 18:33 ` Firewire gaxt
2003-07-25 16:28 ` Firewire gaxt
2003-07-25 15:53 ` Firewire Chris Ruvolo
2003-07-25 15:47 ` Firewire Ben Collins
2003-07-25 16:14 ` Firewire Chris Ruvolo
2003-07-25 13:34 ` Firewire Ben Collins
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=20030726174537.GF490@phunnypharm.org \
--to=bcollins@debian.org \
--cc=gaxt@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sbromley@cogeco.ca \
--cc=thoffman@arnor.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.