...

...

Enclosed are two patches. The clean patch is for a clean VDR 1.7.0 source tree patched with Reinhard's vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 patch. The patched patch is for those who have used the patch from 04-10-2008.

I'm about to begin setting up my new VDR with DVB-S2 support, so I was wondering

• where is the ultimate S2API driver source?

http://linuxtv.org/hg/v4l-dvb/ http://linuxtv.org/hg/~stoth/s2/ http://linuxtv.org/hg/~stoth/s2-mfe/ - s2api with multifrontend support

Steve can you comment the differences between s2 and s2-mfe trees and whether those are planned to be compined in near future?

To my understanding the only difference between s2 and s2-mfe branches is the support for hvr-4000 style of devices. So:

- s2: --> would support only 1 frontend for 1 card at a time. Therefore one would need to select during the driver loading time whether to want to use hvr-4000 in DVB-S/S2 mode or in DVB-T mode.

So in dev-tree following are available:

[root@tinka vdr-1.7.0]# ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 120 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw----+ 1 lamikr video 212, 4 2008-10-05 10:56 demux0 crw-rw----+ 1 lamikr video 212, 5 2008-10-05 10:56 dvr0 crw-rw----+ 1 lamikr video 212, 3 2008-10-05 10:56 frontend0 crw-rw----+ 1 lamikr video 212, 7 2008-10-05 10:56 net0

- s2-mfe: --> can create multiple fronends for single card eventhoughg only one of those can in reality to be used simultaneously. Thus one does not need to select between DVB-S/S2 mode and DVB-T mode during the driver load time. So following nodes are available:

[root@tinka vdr-1.7.0]# ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 200 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw----+ 1 lamikr video 212, 68 2008-10-05 10:56 demux0 crw-rw----+ 1 lamikr video 212, 84 2008-10-05 10:56 demux1 crw-rw----+ 1 lamikr video 212, 69 2008-10-05 10:56 dvr0 crw-rw----+ 1 lamikr video 212, 85 2008-10-05 10:56 dvr1 crw-rw----+ 1 lamikr video 212, 67 2008-10-05 10:56 frontend0 crw-rw----+ 1 lamikr video 212, 83 2008-10-05 10:56 frontend1 crw-rw----+ 1 lamikr video 212, 71 2008-10-05 10:56 net0 crw-rw----+ 1 lamikr video 212, 87 2008-10-05 10:56 net1

Mika

here are the vdr S2API patches for vdr 1.7.1 + extensions 64 patch and also for the vanilla vdr 1.7.1.

does these patches include the DVB-S, DVB-S2, DVB-T and DVB-C support ?

Goga

here are the vdr S2API patches for vdr 1.7.1 + extensions 64 patch and also for the vanilla vdr 1.7.1.

What is the purpose of this extension 64 patch?

Mika

here are the vdr S2API patches for vdr 1.7.1 + extensions 64 patch and also for the vanilla vdr 1.7.1.

could you release s2api patch for vdr 171 already patched with vdr-1.7.1-ext_h264.diff

i forgott write that the ext64 patch sits on top off :

vdr 1.7.1 + extensions 64 + the h264 patch.

With h264 patch, do you mean that vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff has been ported somewhere for vdr-1.7.1?

Mika

Hi All,

this patches are for Steve Toth's repository at : http://linuxtv.org/hg/~stoth/s2/ . In theory they should work. I did them offline from my VDR.

cu

Edgar (gimli) Hucek

Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:

So as long as these cards are not supported, VDR will not go anywhere near S2API (and I certainly will not support two DVB APIs in parallel).

once again a strong reason to splitt off dvb support into plugins.

clemens

Hi All,

this patches are for Steve Toth's repository at : http://linuxtv.org/hg/~stoth/s2/ . In theory they should work. I did them offline from my VDR.

cu

Edgar (gimli) Hucek

Hi,

I just can't compile my vdr. I applied the following patches to vanilla vdr-1.7.1:

- vdr-1.7.1_extensions.diff - vdr-1.7.1-ext_h264.diff - vdr-1.7.1-s2api-ext64.patch - fix-s2api-dvbs-tuning.patch

Everything worked fine until here. Now I downloaded and installed S2API (from http://linuxtv.org/hg/~stoth/s2-mfe right?).

After setting the paths etc in teh make configs I tried to compile vdr, but this is what happens then:

root@HTPC:/usr/local/src/vdr-1.7.1# make g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DUSE_CMDRECCMDI18N -DUSE_CMDSUBMENU -DUSE_CUTTIME -DUSE_DDEPGENTRY -DUSE_DOLBYINREC -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_PLUGINMISSING -DUSE_SETTIME -DUSE_WAREAGLEICON -DREMOTE_KBD -DVDR_USER="vdr" -DLIRC_DEVICE="/dev/lircd" -DRCU_DEVICE="/dev/ttyS1" -D_GNU_SOURCE -DVIDEODIR="/daten/Video/vdr/video.00" -DCONFDIR="/daten/Video/vdr/video.00" -DPLUGINDIR="./PLUGINS/lib" -DLOCDIR="./locale" -DUSE_PLUGINAPI -I/usr/include/freetype2 -I../s2-mfe/linux/include channels.c channels.c:70: error: 'NBC_QPSK' was not declared in this scope channels.c:71: error: '_8PSK' was not declared in this scope channels.c:72: error: '_16APSK' was not declared in this scope channels.c: In member function 'void cChannel::SetLinkChannels(cLinkChannels*)': channels.c:690: warning: format not a string literal and no format arguments make: *** [channels.o] Fehler 1

Any ideas?

Regards Martin Schlosser

you are using the older patch use the attached one. The fix-s2api-dvbs is not needed with this one.

I have some comment from these patches as I tried to investigate the code to find out why it does not work with my hvr-1300 and hvr-4000 in vdr-1.7.1 and xineliboutput. With vdr-1.7.0 version of these patches, the hvr-4000 is able to scan dvb-s channels ok but hvr-1300 fails to scan dvb-t channels.

One thing that looks suspicious is that the code in dvbdevice.c function cDvbDevice::cDvbDevice(int n). I have hvr-1300 (dvb-t) as a first device and hvr-4000 (dvb-t+dvb-s/s2) as a second device.

For hvr-1300 this method reports incorrect transport modes "DVBS DSS", when it should report "DVBT". For hvr-4000 it is reporting the "DVBS2", so it is halfly correct. I think it should report "DVBS2 DVBT" as I am using s2-mfe drivers and thus 2 frontends created under /dev/dvb/adapter1.

Oct 18 00:00:23 tinka vdr: [28627] device 1 provides: DVBS DSS ... Oct 18 00:00:23 tinka vdr: [28627] device 2 provides: DVBS2

I think there are couple of bugs in the code. 1) frontend.h in dvb-b drivers defines following types: typedef enum fe_delivery_system { SYS_UNDEFINED, SYS_DVBC_ANNEX_AC, SYS_DVBC_ANNEX_B, SYS_DVBT, SYS_DVBS, SYS_DVBS2, SYS_DVBH, SYS_ISDBT, SYS_ISDBS, SYS_ISDBC, SYS_ATSC, SYS_ATSCMH, SYS_DMBTH, SYS_CMMB, SYS_DAB, } fe_delivery_system_t;

But in vdr-code those are compared to stings defined in following array:

const char *DeliverySystems[] = { "DVBS", "DSS", "DVBS2", "DVBC", "DVBT", "DVBH", "ATSC", NULL };

So both the order and amount of strings compared is different and I do not understand how this "if (frontendType & (1u << i))" is planned to work.

If I have understood correctly this bug does not however explain why my hvr-1300 does not work, as in the end this for loop is only used for trying to detect whether the frontend type is SYS_DVBS2. For other types it will just printout informative debug.

2) Second problem that comes to my mind is that the code seems to assume that there is only 1 frontend for every adapter available, so it will not detect if card supports for example both dvb-t and dvb-s. I do not know yet, which would be the best place for making changes to support both.

-----Oorspronkelijk bericht----- Van: Klaus.Schmidinger@cadsoft.de [mailto:vdr-bounces@linuxtv.org] Namens Klaus Schmidinger Verzonden: zondag 5 oktober 2008 12:35 Aan: vdr@linuxtv.org Onderwerp: Re: [vdr] [PATCH] S2API for vdr-1.7.0 (05-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)

-- SNIP -- I'm about to begin setting up my new VDR with DVB-S2 support, so I was wondering

Just to get one thing straight. Currently only a couple of DVB-S2 cards are supported. Be sure to check the Wiki of S2API: http://www.linuxtv.org/wiki/index.php/S2API

I read somewhere you used a S2-3200. That is possibly not yet supported. At least, not yet ;)

• where is the ultimate S2API driver source?

Development repo: http://linuxtv.org/hg/~stoth/s2

• can you provide an S2API patch against plain vanilla VDR 1.7.1

(without any other patches)? It should only make the necessary changes to switch from the multiproto API to the S2API.

It's attached :)

Klaus

Regards,

Niels Wagenaar

-----Oorspronkelijk bericht----- Van: Klaus.Schmidinger@cadsoft.de [mailto:vdr-bounces@linuxtv.org] Namens Klaus Schmidinger Verzonden: zondag 5 oktober 2008 17:53 Aan: vdr@linuxtv.org Onderwerp: Re: [vdr] [PATCH] S2API for vdr-1.7.0 (05-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)

-- SNIP -- Apparently stb6100.ko and stb0899.ko are not contained in that driver, which means it's useless for me.

That's correct.

Any idea when these will become part of the S2API driver? IIRC these did work (at least to some extent) in the "multiproto" driver...

According to the announcement, it should be available within 4 weeks after the announcement:

The group aims to have a unified in-kernel DVB-S2 HVR4000 / TT-3200 tree (that also supports all of the derivative CX24116 / STB0899 known products) within 4 weeks from the announcement, hopefully in time for kernel 2.6.28. For that, we would like to ask Manu to port his drivers to the new API.

Klaus

Regards,

Niels Wagenaar

When will DVB-IP be included in the S2API? I'm asking because in South Africa, our chances are looking slim by the moment to implement DVB-T, I reckon by the time we get DVB-T the world has moved over to DVB-T2 and we might skip the whole process over to DVB-IP, I see a lot of streamdev discussions going on here in the vdr mailing list.

On 05/10/2008, Niels Wagenaar n.wagenaar@xs4all.nl wrote:

...

-----Oorspronkelijk bericht----- Van: Klaus.Schmidinger@cadsoft.de [mailto:vdr-bounces@linuxtv.org] Namens Klaus Schmidinger Verzonden: zondag 5 oktober 2008 12:35 Aan: vdr@linuxtv.org Onderwerp: Re: [vdr] [PATCH] S2API for vdr-1.7.0 (05-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)

-- SNIP --

...

I'm about to begin setting up my new VDR with DVB-S2 support, so I was wondering

Just to get one thing straight. Currently only a couple of DVB-S2 cards are supported. Be sure to check the Wiki of S2API: http://www.linuxtv.org/wiki/index.php/S2API

I read somewhere you used a S2-3200. That is possibly not yet supported. At least, not yet ;)

...

• where is the ultimate S2API driver source?

Development repo: http://linuxtv.org/hg/~stoth/s2

...

• can you provide an S2API patch against plain vanilla VDR 1.7.1

(without any other patches)? It should only make the necessary changes to switch from the multiproto API to the S2API.

It's attached :)

...

Klaus

Regards,

Niels Wagenaar

---

vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr