Date: Wed, 20 Aug 2008 09:56:02 -0700 From: Sean Bruno <sbruno@miralink.com> To: Dieter <freebsd@sopwith.solgatos.com> Cc: Scott Long <scottl@samsco.org>, freebsd-firewire@freebsd.org Subject: Re: Something broke :-( Re: fwcontrol update Message-ID: <48AC4CA2.2080801@miralink.com> In-Reply-To: <200808200607.GAA01246@sopwith.solgatos.com> References: <200808200607.GAA01246@sopwith.solgatos.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dieter wrote: >>>>> I notice that it doesn't print every generation. >>>>> I notice that the node_id changes. >>>>> >>>>> >>>> This alarms me quite a bit. I didn't think there was anyway for the >>>> generation to change >>>> without the log message being spit out. Interesting. >>>> >>>> >>> Perhaps there is some register on the controller chip that >>> affects receiving data but not sending it, and isn't getting >>> initialized. Perhaps the controller chip thinks it is receiving >>> bad data, and flags an error or requests a bus reset? >>> >>> If the resets are happening faster than the printf can run, >>> maybe the data (generation number) changes underneath the printf, >>> much like ps/top don't get a pure snapshot? >>> >>> >> Hrm...First, let's try and get your camera working again. >> >> I would like you to try and connect your camera to a Mac, Linux or >> Windows box and try to get it working again. >> > > As far as I can tell the camera is working fine. > > For example I can send DV data *to* the camera over firewire and it > happily converts it to analog and ships it out s-video to the TV. > > And the data *from* the camera is recognized as DV: > > fwcontrol_prev -u 1 -R camera.dv > Detected DV format on input. > (EAGAIN) > (EAGAIN) > (EAGAIN) > > The camera was of course powered off while I tested the argument > range checks. And I only ran tests that seemed safe. I'm not > *completely* insane. > So, is you camera working perfectly at this time? I.e. with old fwcontrol, everything is fine? My concern was that somehow we had triggered a bit in the firewire hardware(most likely the camera) that caused you camera to be non-functional. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48AC4CA2.2080801>