Hi list!
I assume the timeout value is set somewhere in dvbdevice.c (where the "frontend timed out while tuning to channel" message can be found).
Can somebody point me to the right place, where the tuning timeout is actually set?
Thanks!
On Tue, Aug 31, 2010 at 12:29 AM, Stefan tuxoholic@hotmail.de wrote:
Hi list!
I assume the timeout value is set somewhere in dvbdevice.c (where the "frontend timed out while tuning to channel" message can be found).
Can somebody point me to the right place, where the tuning timeout is actually set?
That's a function of the dvb driver. You'll need to edit your driver source, recompile, and reinstall it.
On 31.08.2010 17:50, VDR User wrote:
On Tue, Aug 31, 2010 at 12:29 AM, Stefan tuxoholic@hotmail.de wrote:
Hi list!
I assume the timeout value is set somewhere in dvbdevice.c (where the "frontend timed out while tuning to channel" message can be found).
Can somebody point me to the right place, where the tuning timeout is actually set?
That's a function of the dvb driver. You'll need to edit your driver source, recompile, and reinstall it.
Well, a simple 'grep' would tell you that this message is generated in VDR's dvbdevice.c - and that's also where the timeout values are defined, right at the beginning of that file.
Klaus
On Tue, Aug 31, 2010 at 9:41 AM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
I assume the timeout value is set somewhere in dvbdevice.c (where the "frontend timed out while tuning to channel" message can be found).
Can somebody point me to the right place, where the tuning timeout is actually set?
That's a function of the dvb driver. You'll need to edit your driver source, recompile, and reinstall it.
Well, a simple 'grep' would tell you that this message is generated in VDR's dvbdevice.c - and that's also where the timeout values are defined, right at the beginning of that file.
What about the tuner timeout? If that's set too low in the driver then he'll always get that message. This is the case with the current Genpix driver for example (which V4L has so far ignored the patch to fix it).