On Tuesday 18 December 2007 06:15:51 A. P. Kennedy wrote:
> >>>>> "H" == Hans Verkuil <[EMAIL PROTECTED]> writes:
>
> H> On Monday 17 December 2007 02:43:44 A. P. Kennedy wrote:
> >> I have been having this problem with the latest development
> >> snapshots. Really started with kernel 2.6.22 and the ivtv driver
> >> in the kernel.
> >>
> >> Currently using kernel - 2.6.23.11 v4l-dvd - updated 12/16/2007
> >> to lastest master repository. This version also contains the
> >> ivtvfb module.
> >>
> >> mythtv - latest svn update from today 12/16/2007.
> >>
> >> I have started having the following errors.
> >>
> >> i2c-adapter i2c-3: sendbytes: error - bailout. msp3400 3-0040:
> >> I/O error #0 (read 0x10/0x200) i2c-adapter i2c-3: sendbytes:
> >> error - bailout. msp3400 3-0040: I/O error #0 (read 0x10/0x200)
> >> i2c-adapter i2c-3: sendbytes: error - bailout. msp3400 3-0040:
> >> I/O error #0 (read 0x10/0x200) i2c-adapter i2c-2: sendbytes:
> >> error - bailout. msp3400 2-0040: I/O error #0 (read 0x10/0x200)
> >> i2c-adapter i2c-3: sendbytes: error - bailout. msp3400 3-0040:
> >> I/O error #0 (read 0x10/0x200)
> >>
> >> What does this error mean?
> >>
> >> When this error occurs I lose the sound on the recording, and
> >> wife gets mad ;-)
> >>
> >> It is strange because this error does not happen all the time,
> >> and the next recording usually is okay.
> >>
> >> I did a search of the mailing list, and one user upgrade to the
> >> lastest v4l-dvb to resolve this problem. However, no luck here.
> >> Anything else I can try? Thanks for any help on this matter.
>
> 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.
OK, good news. Can you try to use the values 6, 7, 8 and 9 as well and
see until which value you still get errors? And I also like to know
which msp chip you have (should be in the kernel log).
Thanks,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
