Whats up with “pvrusb2 disagrees about version of symbol tveeprom_hauppauge_analog”?
This is the result of an interaction between CONFIG_MODVERSIONS (a kernel build option) and the horrid hacked up way in which the pvrusb2 driver attempts to deal with tveeprom.ko (see eeprom.html for more about that hack). When CONFIG_MODVERSIONS is in use, the kernel build system generates these per-symbol CRCs by taking into account every aspect related to the symbol’s declaration – like its argument types, the definition of those argument types, the return type, etc. This is done for each symbol exported by a module (a definition) and for each symbol that needs to be imported into a module (a declaration). The idea here is to make sure that the symbol has been defined in precisely the same way it has been declared. If the declaration and definition disagree, then their CRCs won’t match and the module loader catches this, prints that nasty message and aborts the load of the module in question. Obviously if a symbol’s declaration and definition do not match, then there may be an incom
