Hans Verkuil wrote: > On Sun, 2008-03-02 at 23:33 -0500, Andy Walls wrote: > > Hans, > > > > More feedback on the beta cx18 driver....
> Hi Andy, > > Thank you for your research on this. Unfortunately it may take a while > before I can look into this myself as I am currently investigating the > VBI issues with ivtv. Once that's done I'll get back on the cx18 > problems. Since fixing the VBI problems with ivtv is time consuming, so > I do not know exactly when I get back to the cx18. I understand. I did not think you would get to any of the cx18 problems soon, given your previous progress report e-mail. However, I didn't see any harm in putting some problem reports "in the pile" from which you could select to work, when you did have time to revisit the cx18 driver. Plus, if I didn't write them down, I'd forget them. :) I myself have very little time for playing around with software at home. Along with the problem reports, I would normally try to work up patches for you to evaluate. However lack of free time and datasheets makes that difficult. > Also note that the AV digitizer registers of the cx23418 are almost, but > not entirely the same as for the cx2584x. There are some differences in > particular in the handling of the status log. So point 6 in your list > below is not true since the standard IDs have changed in the cx23418. > If it reports BTSC, then it really is BTSC. Yes, I figured the datasheets had to be different in some respects. It makes sense that microcontroller program output enumerations would change. I wish you the best of luck with resolving the VBI bugs. Regards, Andy > Regards, > > Hans > > > > 6. v4l2-ctl --log-status reports an autodetected standard of "BTSC" > > when that status register at 0x02c40805 is reporting "0 - not defined" > > as opposed to "0xF -BTSC" and the microcontroller hasn't bothered to > > unmute any of the audio paths. Reporting BTSC in this situation seems > > misleading, as it doesn't appear that the microcontroller has determined > > the standard yet. > > > > > > -Andy _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
