Hi Steven,
I'm happy to inform you that all failures have vanished.
Summarizing:
I compiled 4.2-RC3 with your patch and with
/* Tri-state the TS bus */
si2168_set_ts_mode(fe, 0);
changed the .delsys line in si2168.c to satisfy MythTV from
.delsys = {SYS_DVBT, SYS_DVBT2, SYS_DVBC_ANNEX_A},
to
.delsys = {SYS_DVBC_ANNEX_A, SYS_DVBT, SYS_DVBT2},
added the dvbloopback module (for descrambling with MythTV) and saa716x
bridge driver (to support my TBS 6285 cards)
Result: lock and tune is just fine in both TVheadend and MythTV with TBS
6285 as well as DVBSky T982 cards.
TBS 6285: saa716x+si2168+si2157
DVBSky T982: cx23885+si2168+si2157
Regards,
Tycho.
Op 21-07-15 om 21:00 schreef Steven Toth:
On Tue, Jul 21, 2015 at 2:07 PM, Tycho Lürsen <tycholursen@xxxxxxxxx> wrote:
Op 21-07-15 om 18:19 schreef Steven Toth:
On Tue, Jul 21, 2015 at 12:11 PM, Tycho Lürsen <tycholursen@xxxxxxxxx>
wrote:
Hi Steven,
I was too curious to wait for you and Antti to settle your differences,
so I
tested again against a 4.2-RC2
I did not disable DVB-T/T2, instead I reordered the lot. MythTV just sees
the first system in the .delsys line in si2168.c,
so when it looks like this:
SYS_DVBC_ANNEX_A, SYS_DVBT, SYS_DVBT2
I'm good.
We have no differences, its Antti's si2168 driver. If Antti doesn't
like the approach for tri-stating, he's free to suggest and
alternative. I suggested two alternatives yesterday.
Result:
With your patch both MythTV and Tvheadend still can't tune. Without it,
everything is ok.
I'm not very interested in czap results, only in real use cases. For me
that's MythTV, but just to be sure I also tested with TVheadend.
That's pretty bizarre results, although thank you for testing. :)
When you say it can't tune, do you mean the signal does not lock, or
that no video appears?
No lock, or partial lock.
Thanks.
That's even worse than expected, given that the patch adjusts the TS
interface, and has nothing to do with tuning, lock, rf or signal
status. It still feels like something else is going on, some other
unexpected race for example.
I can't reproduce that behavior, but given that you can.... Can you
please try this? in si2168.c, change:
/* Tri-state the TS bus */
si2168_set_ts_mode(fe, 1);
to
/* Tri-state the TS bus */
si2168_set_ts_mode(fe, 0);
... recompile and retest?
Thx.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html