Reply to thread

Message

<blockquote data-quote="deeptho" data-source="post: 1126017" data-attributes="member: 215446">And if you would to try to change the demod to rf input assignment, you could look in tbsecp3-dvb.cline 2036 and 2039.Replacetbs6909x_stid135_cfg, adapter-&gt;nr, adapter-&gt;nr/2)withtbs6909x_stid135_cfg, adapter-&gt;nr, adapter-&gt;nr%4)Note that there are two lines: one fr version 1 of the card and 1 for version 2...This will map as follows:adapter 0 and an adapter 4 will be attached to RF0adapter 1 and an adapter 2 will be attached to RF1...This would allow all 4 RF inputs to be used, but still not more than 4 simultaneous fft scans.Obvously, in your user programs you need to use new adapter numbers. E.g., the the old adapter2&nbsp; will now be called adapter1 in tvheadend.It is possible that this will lead to a driver crash, which then indicates a bug in the stid135-fe or stid135_drv code (e.g., some programmer assuming that rf_input == adapter_no/2).If you test this, please report back, because similar changes could be useful for tbs6903x and other cards. This could be implemented as a driver option. In the long term I plan to make the RF to adapter mappingfully configurable, but this requires quite a few changes. This will be more versatile.For instance user space programs will be able to attach all 8 tuners dynamically to any of the inputs.Or switching between tuner_mode will no longer require reloading the drivers.</blockquote>

[QUOTE="deeptho, post: 1126017, member: 215446"] And if you would to try to change the demod to rf input assignment, you could look in tbsecp3-dvb.c line 2036 and 2039. Replace tbs6909x_stid135_cfg, adapter->nr, adapter->nr/2) with tbs6909x_stid135_cfg, adapter->nr, adapter->nr%4) Note that there are two lines: one fr version 1 of the card and 1 for version 2... This will map as follows: adapter 0 and an adapter 4 will be attached to RF0 adapter 1 and an adapter 2 will be attached to RF1 ... This would allow all 4 RF inputs to be used, but still not more than 4 simultaneous fft scans. Obvously, in your user programs you need to use new adapter numbers. E.g., the the old adapter2 will now be called adapter1 in tvheadend. It is possible that this will lead to a driver crash, which then indicates a bug in the stid135-fe or stid135_drv code (e.g., some programmer assuming that rf_input == adapter_no/2). If you test this, please report back, because similar changes could be useful for tbs6903x and other cards. This could be implemented as a driver option. In the long term I plan to make the RF to adapter mapping fully configurable, but this requires quite a few changes. This will be more versatile. For instance user space programs will be able to attach all 8 tuners dynamically to any of the inputs. Or switching between tuner_mode will no longer require reloading the drivers. [/QUOTE]

Verification