On Sat, 2008-09-13 at 16:38 -0400, Rick wrote:
> Andy Walls wrote:
> > On Sat, 2008-09-13 at 09:25 -0400, Rick wrote:
> >
> >
> Hi Andy,
> 
> Thanks for the response.  Is there command I can issue that will display
> whether the Z8 chip is present or not?  The PC is in a hard to reach
> place.

Yes you must have i2cdetect intstalled from the lm_sensors or i2c-tools
package.  You must also have the i2c-dev module built.  Modprobe the
i2c-dev module, have i2cdetect list the busses, then run i2cdetect to
check for the Z8 chip on each ivtv i2c bus.


# modprobe i2c-dev

# i2cdetect -l
i2c-0   smbus           SMBus PIIX4 adapter at 0b00             SMBus adapter
i2c-1   i2c             ivtv i2c driver #0                      I2C adapter
i2c-2   i2c             cx18 i2c driver #0-0                    I2C adapter
i2c-3   i2c             cx18 i2c driver #0-1                    I2C adapter

# i2cdetect 2 0x70 0x71
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2.
I will probe address range 0x70-0x71.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30:                                                 
40:                                                 
50:                                                 
60:                                                 
70: 70 71                                           
   (^^^^^ My HVR-1600 has an IR-blaster)

# i2cdetect 1 0x70 0x71
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x70-0x71.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30:                                                 
40:                                                 
50:                                                 
60:                                                 
70: -- --                                           
   (^^^^^ My PVR-150MCE doesn't have an IR blaster)


Regards,
Andy


> I'm including the message log output in the hopes that will be helpful.
> 
> kernel: ivtv:  ==================== START INIT IVTV ====================
> kernel: ivtv:  version 1.0.0 (2.6.22.18-desktop-1mdv SMP mod_unload 686
> ) loading
> kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> kernel: ivtv0: Encoder revision: 0x02060039
> kernel: tveeprom 0-0050: Hauppauge model 26032, rev C199, serial# 8182327
> kernel: tveeprom 0-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> kernel: tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> kernel: tveeprom 0-0050: audio processor is CX25841 (idx 35)
> kernel: tveeprom 0-0050: decoder processor is CX25841 (idx 28)
> kernel: tveeprom 0-0050: has no radio, has IR receiver, has IR transmitter
> kernel: ivtv0: Autodetected Hauppauge WinTV PVR-150
> kernel: ivtv0: reopen i2c bus for IR-blaster support
> kernel: tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> kernel: cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> kernel: cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> kernel: wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
> kernel: tuner 0-0061: type set to 50 (TCL 2002N)
> kernel: ivtv0: Registered device video0 for encoder MPEG (4 MB)
> kernel: ivtv0: Registered device video32 for encoder YUV (2 MB)
> kernel: ivtv0: Registered device vbi0 for encoder VBI (1 MB)
> kernel: ivtv0: Registered device video24 for encoder PCM audio (1 MB)
> kernel: ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> kernel: ivtv:  ======================  NEXT CARD  ======================
> kernel: ivtv1: Autodetected Hauppauge card (cx23416 based)
> kernel: ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
> kernel: ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> kernel: ivtv1: Encoder revision: 0x02060039
> kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> kernel: cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
> kernel: cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> kernel: wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> kernel: tveeprom 2-0050: Hauppauge model 26032, rev C199, serial# 8162573
> kernel: tveeprom 2-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> kernel: tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
> kernel: tveeprom 2-0050: audio processor is CX25841 (idx 35)
> kernel: tveeprom 2-0050: decoder processor is CX25841 (idx 28)
> kernel: tveeprom 2-0050: has no radio, has IR receiver, has IR transmitter
> kernel: ivtv1: Autodetected Hauppauge WinTV PVR-150
> kernel: ivtv1: reopen i2c bus for IR-blaster support
> kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> kernel: cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
> kernel: cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> kernel: wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> kernel: tuner 2-0061: type set to 50 (TCL 2002N)
> kernel: ivtv1: Registered device video1 for encoder MPEG (4 MB)
> kernel: ivtv1: Registered device video33 for encoder YUV (2 MB)
> kernel: ivtv1: Registered device vbi1 for encoder VBI (1 MB)
> kernel: ivtv1: Registered device video25 for encoder PCM audio (1 MB)
> kernel: ivtv1: Initialized Hauppauge WinTV PVR-150, card #1
> kernel: ivtv:  ====================  END INIT IVTV  ====================
> kernel: lirc_dev: IR Remote Control driver registered, major 61
> kernel: lirc_pvr150: chip found with RX and TX
> kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
> kernel: lirc_pvr150: firmware of size 302355 loaded
> kernel: lirc_pvr150: 743 codesets loaded
> lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
> lirc_pvr150: ivtv i2c driver #1: no devices found
> 
> 
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> 


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

Reply via email to