<div class="gmail_extra"><div class="gmail_quote">On 1 May 2012 12:18, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 30/04/12 22:10, Niklas Brunlid wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
One week with no replies, figured I'd bump this at least once. :)<br></div><div class="im">
On 23 April 2012 10:01, Niklas Brunlid<<a href="mailto:prefect47@gmail.com" target="_blank">prefect47@gmail.com</a>> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><div class="im">
Apologies for cross-posting to the dev list, but it seemed appropriate.<br>
<br>
I'm wondering if there are any plans for support of multi-standard<br>
frontends? I came across<br>
<a href="http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/45723/match=290ewhen" target="_blank">http://article.gmane.org/<u></u>gmane.linux.drivers.video-<u></u>input-infrastructure/45723/<u></u>match=290ewhen</a><br>
looking for clues as to why my PCTV 290e stopped working when I upgraded my<br>
Fedora 15 (now 16) combined backend/frontend server to a 3.x kernel and it<br>
mentions that it was introduced in Linux DVB API v5.4 or something.<br>
<br>
</div></blockquote>
<br>
</blockquote>
I think you'll have to explain in a little more detail exactly what your problem is, if you want someone to look at it. I run a back end with 2xDVB-T cards and a PCTV-290e USB dongle for HD and I have no problems at all. I'm running a Debian 3.0.x kernel on that box.<br>
<br>
Where exactly does your front end enter into this? Tuners are in back end(s). If you mean you have a problem displaying SD/HD content, that's got nothing to do with your tuners.<span class="HOEnZb"><font color="#888888"></font></span><br>
</blockquote><div><br>My mail was basically a shot in the dark since my 290e doesn't work since the upgrade. Sorry for the confusion - I don't mean frontend as in the MythTV frontend, but as the device in /dev/dvb/adapterN/<b>frontend</b>N.<br>
<br>As I understand it, in the new Linux DVB API, the /dev/dvb/adapterN/frontend is no longer split into frontend0 and frontend1 if your device is multi-standard. The 290e supports DVB-T2 and DVB-C on the same input but has to be told which one to use, and earlier this was solved by having device 0 represent DVB-T2 and device 1 represent DVB-C. Although you had to trick it by symlinking all the other devices - demux0, dvr0 and net0 - to demux1, dvr1 and net1, since only frontend1 was created.<br>
<br>In the new API the application has to know about the change, and explicitly tell the device to switch between the standards. From my limited understanding it might be something like <a href="http://www.linuxtv.org/wiki/index.php/S2API">http://www.linuxtv.org/wiki/index.php/S2API</a> that has to be used?<br>
<br>Since this change, my box can no longer use the 290e DVB-C for input. Maybe it works on your system because you use DVB-T2?<br><br>BTW, I also found some discussions specifically about the 290e here: <a href="http://www.mail-archive.com/linux-media@vger.kernel.org/msg31845.html">http://www.mail-archive.com/linux-media@vger.kernel.org/msg31845.html</a><br>
<br>I did get dvbscan or w_scan or something to work against /usr/share/dvb/DVB-C/se-comhem last week, although it seems to use DVB-C2. w_scan claims support for Linux DVB API 5.3 and says that the device is buggy:<br><br>
<br>$ w_scan -A2 -fc -cSE -G -X |tee .czap/channels.conf<br>w_scan version 20120112 (compiled for DVB API 5.3)<br>using settings for SWEDEN<br>DVB cable<br>DVB-C<br>scan type CABLE, channellist 7<br>output format czap/tzap/szap/xine<br>
WARNING: could not guess your codepage. Falling back to 'UTF-8'<br>output charset 'UTF-8', use -C <charset> to override<br>Info: using DVB adapter auto detection.<br> /dev/dvb/adapter0/frontend0 -> CABLE "Sony CXD2820R": very good :-))<br>
<br>Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0)<br>-_-_-_-_ Getting frontend capabilities-_-_-_-_<br>Using DVB API 5.5<br>frontend 'Sony CXD2820R' supports<br>DVB-C2<br>INVERSION_AUTO<br>QAM_AUTO<br>
FEC_AUTO<br>FREQ (45.00MHz ... 864.00MHz)<br>This dvb driver is *buggy*: the symbol rate limits are undefined - please report to <a href="http://linuxtv.org">linuxtv.org</a><br>-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_<br>
73000: sr6900 (time: 00:00) sr6875 (time: 00:05)<br><br><br><br>/ Niklas<br><br></div></div></div>