> Hmm.  I really though the problem could have been that.  Here's my
> rationale:
> 
> 1.  From my dmesg output, the cx18 driver talks to the i2c devices in
> the following order at initialization:
> 
> EEPROM chip
> Analog tuner chips
> CS5345 audio digitizer/multiplexer chip
> MXL5005S chip
> S5H1490 chip
> 
> 2. From your dmesg output, normally the CS5345 is the first device to
> actually respond properly.  That would suggest accessing the CS5345 or
> the analog tuner somehow clears up the I2C bus problem.
> 
> 3.  A similar sequence of mdelay()'s is used in cx23885/cx23885-cards.c
> for the HVR-1200, HVR-1400, HVR-1500, HVR-1700, and HVR-1800 to reset
> the analog tuner.
> 
> 4. You have a different analog tuner (Philips FM1236 MK5 idx 116, type
> 43) than I (TCL M2523_5N_E idx 112, type 50), so perhaps it needs a
> longer delay to be ready after reset.  Or since yours seems to have FM
> radio, and mine doesn't, we might be missing a reset line for a tuner
> chip.
> 
> 
> 
> 
> 
> Since we've got that one good EEPROM read from May 10th, you can use
> some command line options to try and get your card working:
> 
> # modprobe -r cx18
> # modprobe tveeprom debug=1
> # modprobe cx18 cardtype=1 tuner=43 radio=1 ntsc=M
> 

I tried this with the latest patch you sent me, and only that patch.  After 
running dmesg, eeprom error still occurs.  I know there is extra information in 
the middle (extra as in not relating to the TV Tuner), but I'm not going to 
remove it, as I'm afraid I may accidentally remove something important.

http://h1.ripway.com/hendrick/TV.txt


Thanks again.


      

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to