[mythtv] firewire branch status?

[Steven Adeff]

On 4/1/07, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
> On 4/1/07, Steven Adeff <adeffs.mythtv at gmail.com> wrote:
> > On 4/1/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> > > On Sun, 2007-04-01 at 11:36 -0700, Jim Westfall wrote:
> > > > Steven Adeff <adeffs.mythtv at gmail.com> wrote [04.01.07]:
> > > > > Daniel/etc,
> > > > >
> > > > >  Recently Comcast where I live has removed all signs of 5C over
> > > > > firewire for my box so I've begun playing around with firewire
> > > > > capture. Today I downloaded and compiled the firewire branch from SVN
> > > > > (on both my master backend and my frontend since it appears that the
> > > > > firewire branch uses 32, current trunk uses 33 and fixes uses
> > > > > 31......). The setup seems to work fine and the GUID system is quite
> > > > > cool. The only problem is, where with fixes I can easily record over
> > > > > firewire, with the firewire branch I can't.
> > > > >
> > > > > So I'm wondering if the branch is in a flux state or if I should be
> > > > > able to record over firewire, and if so, what information I can gather
> > > > > for you to figure out what's going wrong?
> > > > >
> > > >
> > > > The firewire branch was merged back into head/trunk a couple months ago.
> > >
> > > There were a couple more changes in the branch, but since I no
> > > longer have a firewire cable box those won't be developed any
> > > further, at least by me. Using SVN head is the best option at
> > > this point and I'll delete the firewire branch when I have a
> > > little more time on my hands to do MythTV stuff.
> >
> > thanks guys, I'll compile SVN head on my frontend and report back.
> >
> > Daniel, if theres any help I can provide for  you in finishing off
> > those couple changes let me know, I'm using the firewire on a remote
> > backend so I can play around with that backend.
>
> ok, all seems to be working, though I'm getting
>
> 2007-04-01 16:14:08.254 TFW, Error: Write() -- IOBOUND begin cnt(9400)
> free(4335)
> 2007-04-01 16:14:08.556 TFW, Error: Write() -- IOBOUND end
> ...
> 2007-04-01 16:14:08.254 TFW, Error: Write() -- IOBOUND begin cnt(9400)
> free(4335)
> 2007-04-01 16:14:08.556 TFW, Error: Write() -- IOBOUND end
> 2007-04-01 16:20:10.335 TFW, Error: Write() -- IOBOUND begin cnt(9400)
> free(4335)
> 2007-04-01 16:20:10.754 TFW, Error: Write() -- IOBOUND end
>
> in the log output of the backend recording firewire, which I don't
> remember seeing before. Its recording to a nfs mounted recording drive
> on my master backend machine.
>
> Is this something I should be concerned with?

Hi guys, been running this a while and its been great. One thing I
noticed, the box got reset  and it changed ports. Myth found it fine
with the GUID system but recordings didn't work. I had to run the
firewire_tester -B command a couple times on the box at the new port
to get it working again. Is the method firewire_tester uses included
in part of how Myth internally handles firewire recordings?

-- 
Steve
Before you ask, read the FAQ!
http://www.mythtv.org/wiki/index.php/Frequently_Asked_Questions
then search the Wiki, and this list,
http://www.gossamer-threads.com/lists/mythtv/
Mailinglist etiquette -
http://www.mythtv.org/wiki/index.php/Mailing_List_etiquette