On Monday 10 October 2005 22:13, Larry K wrote:
> I now have the right version of the ivtv driver loading. To do this I had
> to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the
> driver properly. I was using 2.6-10.x and there appears to be no
> prepackaged ivtv 0.3.x driver for this kernel.
>
> Now, having gotten the ivtv driver corrected, I seem to have introduced
> another problem with a number of unknown symbols, as shown below in dmesg
> output. Can anyone shed any light on this?
>
> I also read that the ivtv version of tuner, tveeprom, and msp3400 must be
> used. I played around with renaming the kernel version of the drivers, in
> an attempt to force the system to laod the ivtv version. But I put
> everything back to the way it was at the start, and below is the modinfo
> output. I am concerned that perhaps I am not loading the correct version of
> these modules?
>
> Many thanks from a frustrated PVR-500 owner.
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog
> cx88xx: Unknown symbol tveeprom_hauppauge_analog
Well, I do know what is wrong, but I don't know why you are bitten by it. The
tveeprom_hauppauge_analog() function in tveeprom.c has an extra client
argument in the upcoming 2.6.14 kernel. However, it looks like your kernel
has that extra argument already. Can you check tveeprom.c from your kernel
tree (it should be in drivers/media/video) and report if the function looks
like this:
void tveeprom_hauppauge_analog(struct i2c_client *c, struct tveeprom *tvee,
unsigned char *eeprom_data)
or this:
void tveeprom_hauppauge_analog(struct tveeprom *tvee, unsigned char
*eeprom_data)
Note the extra i2c_client pointer in the first. One option is not to use the
ivtv tveeprom but the one from the kernel. This should work. Alternatively
you can edit tveeprom.c in ivtv to add the 'struct i2c_client *c' argument.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
