On Sun, 27 Feb 2005, James L. Reese wrote:

Agreed, and I've spent about three weeks worth of spare time bit-banging the driver and I have so far found no combination of register settings that affect either one of these problems. Based on i2c captures from a windows machine, if everything is doing what it says it's doing, we should be sending the right data to the card but apparently not. I have no way to i2c capture on my Linux system so I can't compare the raw data.
I still think there is something fundamental wrong like a firmware problem or an error in the register map or something like that, but without more data from Conexant/Hauppauge, we're probably stuck trying to fix it the hard way...

Could this be a timing/order problem? I.e. if the registers has to be "poked" in a certain order or within a certain time...


Best regards

Peter K



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to