[pvrusb2] Test : Compile with 2.6.14-rc1

Mike Isely isely at isely.net
Mon Sep 19 23:55:16 CDT 2005

I think I know about this problem.

I've been talking to the current official V4L maintainer over the past
week or so, and just last Saturday I pointed out to him about the fact
that the tveeprom code doesn't provide a proper way to retrieve the device
serial number (it's in the eeprom and it is being parsed out but there's
no official API to get at it).  The pvrusb2 driver has to get this by
calling an "internal" function.  He then mentioned that the eeprom parsing
code has been considerably updated in 2.6.14 - which is another way to say
that it has been changed.

I need to examine this and determine the nature of the change.  It will
probably end up being incompatible with the included tveeprom.c source in
the pvrusb2 driver, which means I have to decide how to handle this


On Mon, 19 Sep 2005 xavier.gnata at free.fr wrote:

> Hi,
> I just have tested to compiled a 2.6.14-rc1 : This seems to works just fine on
> my box.
> I have of course try to compile the pvrusb2 driver and it failled in a quite
> strange way :
> root at dupilon:/usr/local/pvrusb2-mci-20050911/driver#make
> make INSTALL_MOD_DIR=pvrusb2 -C /lib/modules/2.6.14-rc1-1/build
> M=/usr/local/pvrusb2-mci-20050911/driver modules
> make[1]: Entering directory `/usr/src/linux-2.6.14-rc1'
>   CC [M]  /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-msp34x5g.o
>   CC [M]  /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-encoder.o
>   CC [M]  /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-saa7115.o
>   CC [M]  /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.o
> /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.c: In function
> 'pvr2_eeprom_analyze':
> /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.c:86: warning: passing
> argument 1 of 'tveeprom_hauppauge_analog' from incompatible pointer type
> /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.c:86: warning: passing
> argument 2 of 'tveeprom_hauppauge_analog' from incompatible pointer type
> /usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.c:86: error: too few
> arguments to function 'tveeprom_hauppauge_analog'
> make[2]: *** [/usr/local/pvrusb2-mci-20050911/driver/pvrusb2-eeprom.o] Error 1
> make[1]: *** [_module_/usr/local/pvrusb2-mci-20050911/driver] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.14-rc1'
> make: *** [modules] Error 2
> I quite tired this week... so I would like someone else to test once again and
> say us if it works or not. If it doesn't, I will try to chase down this bug.
> xavier.
> ps : Why is there no *simple and complete* api kernel changelog when a new
> kernel version is released?? The kernel api are not stable at all (ok, that is
> the way the kernel is developed. Great) but it *should* (shall?) be
> documented...
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

                        |         Mike Isely          |     PGP fingerprint
     Spammers Die!!     |                             | 03 54 43 4D 75 E5 CC 92
                        |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                        |                             |

More information about the pvrusb2 mailing list