>>>>> "Hans" == Hans Verkuil <[EMAIL PROTECTED]> writes:
H> Just about the only thing that could cause this would be an i2c H> timing change. Use the v4l-dvb repository, edit file ivtv-i2c.c, H> search for this line: >> H> .udelay = 5, >> H> and replace the 5 with 10. Try again and see if this solves the H> problem. Please let me know the result. >> H> The i2c timings were changed to speed up the firmware load, but H> this might have introduced problems in this area. >> H> Regards, >> H> Hans >> H> _______________________________________________ ivtv-devel >> mailing H> list [email protected] H> http://ivtvdriver.org/mailman/listinfo/ivtv-devel >> Thanks that did the trick. Usually this error would occur within >> 10-20 minutes after a recording would start. No error after >> recording for several hours tonight, and no problems with audio >> recordings have been noted. Hans> OK, good news. Can you try to use the values 6, 7, 8 and 9 as Hans> well and see until which value you still get errors? And I also Hans> like to know which msp chip you have (should be in the kernel Hans> log). Hans> Thanks, Hans> Hans Forgot. Here is the chipset information: tveeprom 0-0050: audio processor is MSP4448 (idx 27) tveeprom 0-0050: decoder processor is SAA7115 (idx 19) tveeprom 0-0050: has radio, has IR receiver, has no IR transmitter ivtv0: Autodetected Hauppauge WinTV PVR-350 saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0) msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) msp3400 0-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect I have three cards - two pvr-350's, and one pvr-250. The above information is the same for all cards. Most recordings are done by the card listed above. Thanks Alan _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
