Re: tveeprom build failing after bytesex patches

Jarod Wilson <jarod@xxxxxxxxxxxx> · Sat, 12 Mar 2005 18:44:00 -0800

On Saturday 12 March 2005 15:07, sean darcy wrote:
> I trying to build 2.6.11-bk8 with the 2.6.11-2 patches from
> bytesex.org so I can use the or51132 driver for the pchdtv3000.
>
> The build fails:
>
>   CC [M]  drivers/media/video/btcx-risc.o
>   CC [M]  drivers/media/video/tveeprom.o
> drivers/media/video/tveeprom.c:194: error:
> `TUNER_PHILIPS_FQ1216AME_MK4' undeclared here (not in a funct ion)
> drivers/media/video/tveeprom.c:194: error: initializer element is not
> constant drivers/media/video/tveeprom.c:194: error: (near initialization
> for `hauppauge_tuner[91].id')
> drivers/media/video/tveeprom.c:194: error: initializer element is not
> constant drivers/media/video/tveeprom.c:194: error: (near initialization
> for `hauppauge_tuner[91]')
> drivers/media/video/tveeprom.c:195: error: `TUNER_PHILIPS_FQ1236A_MK4'
> undeclared here (not in a functio n)
> drivers/media/video/tveeprom.c:195: error: initializer element is not
> constant drivers/media/video/tveeprom.c:195: error: (near initialization
> for `hauppauge_tuner[92].id')
> drivers/media/video/tveeprom.c:195: error: initializer element is not
> constant
>
> Any suggestions?

Yeah. The i2c-tuner patch is missing a few lines needed to work with the 
tveeprom updates. A 2.6.11-3 patch is probably in order to correct that. Take 
a look at the latest v4l snapshot, its got the necessary bits in it. (In 
particular, the additional tuner defs in tuner-simple.c and tuner.h for types 
55 through 57).

-- 
Jarod Wilson
jarod@xxxxxxxxxxxx