[mythtv-commits] Ticket #12185: CI/CAM: CAM thread started too late causing "TL__"

[MythTV]

#12185: CI/CAM: CAM thread started too late causing "TL__"
--------------------------------------+-------------------------
     Reporter:  ast@…                 |      Owner:
         Type:  Bug Report - General  |     Status:  new
     Priority:  minor                 |  Milestone:  unknown
    Component:  MythTV - General      |    Version:  Unspecified
     Severity:  medium                |   Keywords:
Ticket locked:  0                     |
--------------------------------------+-------------------------
 This is for mythtv 0.27.1.

 I do have a CAM that, after power up, doesn't pass the transport stream,
 either encrypted or unencrypted, until communication with the CAM
 commences. I didn't check further, which part of the communication (e.g.
 connection, session, time/date) is actually required. A quick look through
 the spec doesn't seem to disallow this CAM behaviour.

 The problem is now, that MythTV starts the CAM thread which commences
 communication only in SetPMT(). This, however, is called only after
 TuningSignalCheck() returns "good signal" which in turn requires the
 transport stream, thus causing a chicken and egg problem resulting in
 "TL__".

 Thus the CAM thread needs to be started before TuningSignalCheck() starts
 to wait for the transport stream.

 The attached patch is more or less a demo workaround that calls SetPMT
 with a NULL PMT before TuningSignalCheck() is called. What is probably
 really required is just to start the CAM thread at a suitable point in the
 processing flow.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12185>
MythTV <http://www.mythtv.org>
MythTV Media Center