Have done some more reboot testing, and the stability is continuing - to a degree.
Problems that are still occuring: 1. The tveeprom on i2c 0x0050 sometimes reports errors: tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. -although this doesn't seem to affect operation 2. The i2c tuner device fails to register, before IVTV goes looking for it: i2c_adapter i2c-0: adapter [ivtv i2c driver #0] registered i2c_adapter i2c-0: client [tveeprom] registered with bus id 0-0050 tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. ivtv0: No tuner detected, default to NTSC tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) Is there a way to force IVTV to wait, or check all the i2c devices have registered?? ----- Original Message ----- From: "Simon Baxter" <[EMAIL PROTECTED]> To: "Discussion list for development of the IVTV driver" <[email protected]> Sent: Thursday, June 01, 2006 12:28 PM Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0 > I'm now running kernel 2.6.17-rc5, which included a bunch of patches > relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then recompiled > the ivtv and v4l-dvb sources from svn. I'm tempting fate saying this, but > seem to be experiencing a period of stability - except for a couple of > errors around: > tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a > Hauppauge eeprom. > > > > Biggest difference I've noticed with this combination is the order the i2c > devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they were: > Installed I2C busses: > i2c-1 unknown ivtv i2c driver #0 Algorithm unavailable > i2c-0 unknown SMBus Via Pro adapter at 5000 Algorithm > unavailable > > > > with 2.6.17-rc5 and GCC 4.1.1 they're: > Installed I2C busses: > i2c-1 unknown SMBus Via Pro adapter at 5000 Algorithm > unavailable > i2c-0 unknown ivtv i2c driver #0 Algorithm unavailable > > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
