mirror of
https://github.com/tuxbox-fork-migrations/recycled-ni-libstb-hal.git
synced 2025-08-26 15:02:43 +02:00
spark: work around neutrino's sectionFilter() usage
It seems like most of the times, timeout == 0 means "use the default
timeout". However, at least with the sectionsd eit update filter and
the PMT version update filter, timeout == 0 means really "no timeout"
alas "infinite". Work around this by using the default timeout only
if no negative filtermask is given.
This fixes the "EPG on program change" (and PMT update probably, too).
Origin commit data
------------------
Branch: master
Commit: 12b74e6ef3
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-02-26 (Sun, 26 Feb 2012)
------------------
This commit was generated by Migit
This commit is contained in:
@@ -372,7 +372,10 @@ bool cDemux::sectionFilter(unsigned short pid, const unsigned char * const filte
|
||||
break;
|
||||
// return -1;
|
||||
}
|
||||
if (timeout == 0)
|
||||
/* the negmask == NULL is a hack: the users of negmask are PMT-update
|
||||
* and sectionsd EIT-Version change. And they really want no timeout
|
||||
* if timeout == 0 instead of "default timeout" */
|
||||
if (timeout == 0 && negmask == NULL)
|
||||
s_flt.timeout = to;
|
||||
|
||||
lt_debug("%s #%d pid:0x%04hx fd:%d type:%s len:%d to:%d flags:%x flt[0]:%02x\n", __func__, num,
|
||||
|
Reference in New Issue
Block a user