[vdr] Small patch for unused TOT

[Andreas Trauer <vdr@trauers.homelinux.net>]

Hi,

in eit.c in method  cSIProcessor::Action() the Time Offset Table is not 
evaluated therefore its filter should not be activated in 
cSIProcessor::SetStatus(). When this is disabled then there is no 
problem with the dsyslog line anymore, that once was printed with every 
TOT packet.

BTW: Why is the filter mask set to 0xfe for the EITs (0x50/0x60)? The 
ETSI standard says 0x50-0x5F and 0x60-0x6F are usable for event 
information. Are any other documents specifying only the first two table 
IDs per type as relevant? I would suggest to extend it to mask 0xf0, but 
that makes more changes in the code necessary, that expects only 
0x50/0x51 and 0x60/0x61.

Andreas

--- eit.c       2003-05-29 17:04:10.000000000 +0200
+++ eit.c.new   2003-10-07 07:32:52.000000000 +0200
@@ -1166,7 +1166,6 @@
   {
      AddFilter(0x00, 0x00);  // PAT
      AddFilter(0x14, 0x70);  // TDT
-      AddFilter(0x14, 0x73);  // TOT
      AddFilter(0x12, 0x4e, 0xfe);  // event info, 
actual(0x4e)/other(0x4f) TS, present/following
      AddFilter(0x12, 0x50, 0xfe);  // event info, actual TS, 
schedule(0x50)/schedule for another 4 days(0x51)
      AddFilter(0x12, 0x60, 0xfe);  // event info, other  TS, 
schedule(0x60)/schedule for another 4 days(0x61)
@@ -1301,10 +1300,8 @@
                                 ctdt.SetSystemTime();
                              }
                           }
-                              /*XXX this comes pretty often:
                           else
                              dsyslog("Time packet was not 0x70 but 
0x%02x\n", (int)buf[0]);
-                              XXX*/
                           break;

                        case 0x12:




--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.