[mythtv] firewire branch status?

Steven Adeff adeffs.mythtv at gmail.com
Tue Apr 24 22:11:49 UTC 2007

On 4/24/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Tue, 2007-04-24 at 17:59 -0400, Steven Adeff wrote:
> > On 4/24/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> > > Well it would have to be testing for data since resets are just
> > > as likely to stop the FireWire from working as to make it work.
> > > Really someone should look closely at the Linux driver and
> > > figure out why the first reset usually doesn't work, on OS X
> > > a reset usually works (they do one whenever a program using
> > > firewire exits, so their implementation has its own problems.)
> >
> > so would implementing something along the lines of what
> > firewire_tester does work? ie. check if data can be properly read, run
> > a fix if not, and run a bus
> > reset if required?
> Not really, the firewire_tester doesn't do resets when data
> can't be read. It's more like you have to do what MythTV does
> when you change that "#if 0" to "#if 1".

ok, well, I'll leave that in, move the boxes and hope a reset isn't
required in the middle of one box's recording =D

> > Obviously from what you said this wouldn't
> > necessarily be as ideal as "fixing" the linux driver, but may be a
> > good work around until then?
> The work around until the driver is fixed is to change that #if.
> Fixing the Linux driver would probably not be a huge amount of
> work. It's a user space driver for the most part, it is just
> that the guy who wrote it is really busy and I don't have a
> firewire recorder anymore.

ah the ol' linux crutch...

thanks Daniel!

Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -

More information about the mythtv-dev mailing list