On 05/20/2012 11:12 PM, Thomas Mair wrote: > On 20.05.2012 22:08, Antti Palosaari wrote: >> On 20.05.2012 20:04, poma wrote: >>> After hard/cold boot: >> >>> DVB: register adapter0/net0 @ minor: 2 (0x02) >>> rtl2832u_frontend_attach: >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> rtl28xxu_ctrl_msg: failed=-32 >>> No compatible tuner found >> >> These errors are coming from tuner probe. As it still goes to probing and >> did not jump out earlier when gate is opened it means that demod is >> answering commands but tuner are not. >> >> My guess is that tuner is still on the reset or not powered at all. It is >> almost 100% sure error is wrong tuner GPIO. > > There is an issue with GPIO, as FC0012 tuner callback will set > the value of one of the GPIO outputs. However fixing that, will > not resolve the issue. So I need to debug the problem further. > True. Whatever a value is changed - 'rtl2832u_power_ctrl', it brakes even more. Precisely, what breaks a tuner on next soft [re]boot are apps/utils which engage tzap/scan[dvb].
· · · — — — · · · cheers, poma -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
