Simon,
Have a look for the file i2c-id.h and check it has the variable
I2C_HW_B_CX2341X set. You might have more than one version of this file on your system. Check to see lirc is using the right one because if the variable is not in the file lirc will compile the code without the wrong probe structure.
Regards,
Michel.
Simon Baxter schreef:
$ diff lirc/drivers/lirc_i2c/lirc_i2c.c lirc\
062106/drivers/lirc_i2c/lirc_i2c.c
< /* $Id: lirc_i2c.c,v 1.38 2006/06/26 23:21:34 lirc Exp $ */
/* $Id: lirc_i2c.c,v 1.37 2006/05/20 04:38:58 lirc Exp $ */
< #ifdef I2C_HW_B_CX2341X
< if (adap->id == (I2C_ALGO_BIT | I2C_HW_B_BT848) ||
< adap->id == (I2C_ALGO_BIT | I2C_HW_B_CX2341X))
< #else
< if (adap->id == (I2C_ALGO_BIT | I2C_HW_B_BT848))
< #endif
< {
---
if (adap->id == (I2C_ALGO_BIT | I2C_HW_B_BT848)) {
Seems to have added some checking for i2c definitions for I2C_HW_B_CX2341X
(kernel 2.6.17+) and I2C_HW_B_BT848. Certainly looks like some updates in
the right areas, but proof will be in the pudding!
Will try it tonight....
There must be something fundamental I'm doing wrong. I get the same
problem:
1010 cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/lirc
login
1011 cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/lirc
co -P lirc
1012 cd lirc/
1019 ./autogen.sh
1025 ./setup.sh
1026 make
1027 make install
1028 depmod
modprobe lirc_dev debug=1
modprobe lirc_i2c debug=1
lircd
lirc_dev: IR Remote Control driver registered, at major 61
lirc_i2c: probe 0x1a @ ivtv i2c driver #0: no
lirc_i2c: probe 0x18 @ ivtv i2c driver #0: no
lirc_i2c: probe 0x71 @ ivtv i2c driver #0: no
lirc_i2c: probe 0x4b @ ivtv i2c driver #0: no
lirc_i2c: probe 0x64 @ ivtv i2c driver #0: no
lirc_i2c: probe 0x30 @ ivtv i2c driver #0: no
lirc_i2c: probe 0x6b @ ivtv i2c driver #0: no
[EMAIL PROTECTED] lirc]# tail /var/log/lircd
Jun 27 19:05:19 media.nzbaxters lircd: accepted new client on /dev/lircd
Jun 27 19:05:19 media.nzbaxters lircd: could not open /dev/lirc
Jun 27 19:05:19 media.nzbaxters lircd: default_init(): No such device
Jun 27 19:05:19 media.nzbaxters lircd: caught signal
Jun 27 19:12:29 media.nzbaxters lircd: lircd(hauppauge) ready
Am I not including something when I compile or something?
I did see this message:
"You should add the contents of `/usr/share/aclocal/libtool.m4' to
`aclocal.m4'."
ivtv seems ok:
Linux video capture interface: v1.00
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.3 (development snapshot compiled on Sat 17 Jun 2006
03:30:00 PM PDT) loading
ivtv: Linux version: 2.6.16.18 686 REGPARM 4KSTACKS gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 21
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
total)
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================
What am I missing here????
_______________________________________________
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
