Date: Tue, 19 Aug 2008 23:07:13 +0100 From: Dieter <freebsd@sopwith.solgatos.com> To: Sean Bruno <sbruno@miralink.com> Cc: Scott Long <scottl@samsco.org>, freebsd-firewire@freebsd.org Subject: Re: Something broke :-( Re: fwcontrol update Message-ID: <200808200607.GAA01246@sopwith.solgatos.com> In-Reply-To: Your message of "Tue, 19 Aug 2008 17:11:01 PDT." <48AB6115.6090308@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200808200607.GAA01246>