<div class="gmail_extra"><div class="gmail_quote">On 1 May 2012 18:55, 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 01/05/12 14:41, 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">
On 1 May 2012 12:18, Mike Perkins<<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.<u></u>org.uk</a>> wrote:<br>
<br>
</div><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>
<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>
On 23 April 2012 10:01, Niklas Brunlid<<a href="mailto:prefect47@gmail.com" target="_blank">prefect47@gmail.com</a>> wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
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>
</div><a href="http://article.gmane.org/**gmane.linux.drivers.video-**" target="_blank">http://article.gmane.org/**<u></u>gmane.linux.drivers.video-**</a><br>
input-infrastructure/45723/**<u></u>match=290ewhen<<a href="http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/45723/match=290ewhen" target="_blank">http://article.<u></u>gmane.org/gmane.linux.drivers.<u></u>video-input-infrastructure/<u></u>45723/match=290ewhen</a>><div class="im">
<br>
looking for clues as to why my PCTV 290e stopped working when I upgraded<br>
my<br>
Fedora 15 (now 16) combined backend/frontend server to a 3.x kernel and<br>
it<br>
mentions that it was introduced in Linux DVB API v5.4 or something.<br>
<br>
<br>
</div></blockquote><div class="im">
I think you'll have to explain in a little more detail exactly what your<br>
</div></blockquote><div class="im">
problem is, if you want someone to look at it. I run a back end with<br>
2xDVB-T cards and a PCTV-290e USB dongle for HD and I have no problems at<br>
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<br>
end(s). If you mean you have a problem displaying SD/HD content, that's got<br>
nothing to do with your tuners.<br>
<br>
</div></blockquote><div class="im">
<br>
My mail was basically a shot in the dark since my 290e doesn't work since<br>
the upgrade. Sorry for the confusion - I don't mean frontend as in the<br></div>
MythTV frontend, but as the device in /dev/dvb/adapterN/*frontend*N.<div><div class="h5"><br>
<br>
As I understand it, in the new Linux DVB API, the<br>
/dev/dvb/adapterN/frontend is no longer split into frontend0 and frontend1<br>
if your device is multi-standard. The 290e supports DVB-T2 and DVB-C on the<br>
same input but has to be told which one to use, and earlier this was solved<br>
by having device 0 represent DVB-T2 and device 1 represent DVB-C. Although<br>
you had to trick it by symlinking all the other devices - demux0, dvr0 and<br>
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<br>
tell the device to switch between the standards. From my limited<br>
understanding it might be something like<br>
<a href="http://www.linuxtv.org/wiki/index.php/S2API" target="_blank">http://www.linuxtv.org/wiki/<u></u>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<br>
it works on your system because you use DVB-T2?<br>
<br>
BTW, I also found some discussions specifically about the 290e here:<br>
<a href="http://www.mail-archive.com/linux-media@vger.kernel.org/msg31845.html" target="_blank">http://www.mail-archive.com/<u></u>linux-media@vger.kernel.org/<u></u>msg31845.html</a><br>
<br>
I did get dvbscan or w_scan or something to work against<br>
/usr/share/dvb/DVB-C/se-comhem last week, although it seems to use DVB-C2.<br>
w_scan claims support for Linux DVB API 5.3 and says that the device is<br>
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<br>
report to <a href="http://linuxtv.org" target="_blank">linuxtv.org</a><br>
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_<u></u>-_-_-_-_-_-_-_-_<br>
73000: sr6900 (time: 00:00) sr6875 (time: 00:05)<br>
<br>
</div></div></blockquote>
Hmm. A strange one.<br>
<br>
micheal@ruby:~$ uname -a<br>
Linux ruby 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012 x86_64 GNU/Linux<br>
micheal@ruby:~$<br>
</blockquote><div><br>Nothing strange about my system:<br>
<br>
<b># modinfo cxd2820r</b><br>
filename: /lib/modules/3.3.2-6.fc16.x86_64/kernel/drivers/media/dvb/frontends/cxd2820r.ko<br>
license: GPL<br>
description: Sony CXD2820R demodulator driver<br>
author: Antti Palosaari <<a href="mailto:crope@iki.fi">crope@iki.fi</a>><br>
depends: i2c-core,dvb-core<br>
intree: Y<br>
vermagic: 3.3.2-6.fc16.x86_64 SMP mod_unload<br>
parm: debug:Turn on/off frontend debugging (default:off). (int)<br>
<br>
<b># uname -a</b><br>
Linux u033 3.3.2-6.fc16.x86_64 #1 SMP Sat Apr 21 12:43:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux<br>
<br>
<b># ls -l /dev/dvb/adapter_290e/</b><br>
total 0<br>
lrwxrwxrwx 1 root root 18 May 1 15:32 demux0 -> ../adapter0/demux0<br>
lrwxrwxrwx 1 root root 16 May 1 15:32 dvr0 -> ../adapter0/dvr0<br>
lrwxrwxrwx 1 root root 21 May 1 15:32 frontend0 -> ../adapter0/frontend0<br>
lrwxrwxrwx 1 root root 16 May 1 15:32 net0 -> ../adapter0/net0<br>
<br>
<b># ls -l /dev/dvb/adapter0</b><br>
total 0<br>
crw-rw----+ 1 root video 212, 5 May 1 15:32 demux0<br>
crw-rw----+ 1 root video 212, 6 May 1 15:32 dvr0<br>
crw-rw----+ 1 root video 212, 4 May 1 15:32 frontend0<br>
crw-rw----+ 1 root video 212, 7 May 1 15:32 net0<br><br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm using DVB-T2, yes. The most recent time I rescanned I noticed that there was a DVB-C option which came up as .../frontend1. This means that I'm not seeing what you are, unfortunately, both my options are still being presented separately.<br>
</blockquote><div><br>Do you still have the frontend1 entry?<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm not sure how this new arrangement you've described works with respect to mythtv. I'd sure like to know, because it's going to bite everyone else who uses the 290e eventually.<br></blockquote><div><br>
If it's a matter of adding support for S2API then it seems to me that there is code out there in several applications already (Kaffeine, VDR, VLC). I think I saw some patch code for some of them, though I didn't understand it :) . But the DVB API docs are not updated from v3 yet.<br>
<br>/ Niklas<br><br></div></div></div>