On Fri, 2009-06-12 at 15:33 -0500, Mike Isely wrote:
> I am unable to reproduce the s5h1411 error here.
>
> However my HVR-1950 loads the s5h1409 module - NOT s5h1411.ko; I wonder
> if Hauppauge has changed chips on newer devices and so you're running a
> different tuner module.
The digital demodulator driver to use is hardcoded in pvrusb2-devattr.c:
static const struct pvr2_dvb_props pvr2_750xx_dvb_props = {
.frontend_attach = pvr2_s5h1409_attach,
.tuner_attach = pvr2_tda18271_8295_attach,
};
static const struct pvr2_dvb_props pvr2_751xx_dvb_props = {
.frontend_attach = pvr2_s5h1411_attach,
.tuner_attach = pvr2_tda18271_8295_attach,
};
...
static const struct pvr2_device_desc pvr2_device_750xx = {
.description = "WinTV HVR-1950 Model Category 750xx",
...
.dvb_props = &pvr2_750xx_dvb_props,
#endif
};
...
static const struct pvr2_device_desc pvr2_device_751xx = {
.description = "WinTV HVR-1950 Model Category 751xx",
...
.dvb_props = &pvr2_751xx_dvb_props,
#endif
};
> That would explain the different behavior.
> Unfortunately it also means it will be very difficult for me to track
> the problem down here since I don't have that device variant.
If you have more than 1 HVR-1950, maybe one is a 751xx variant.
When I ran into I2C errors often, it was because of PCI bus errors
screwing up the bit banging. Obviously, that's not the case here.
-Andy
> -Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
