@udo_richter: "Hi list,
There's a new version of the DVB API wrapper patch that adds fallback 
compatibility to the current stable DVB API without multiproto support.
The new version also fixes a bug with the default DVBFE_MOD_AUTO 
modulation on DVB-S.
Also, the patch for VDR-1.5/1.6 that allows to read a channels.conf from 
1.7 is now available on that page.
Support for DVBFE_SET_DELSYS will follow in next version.
Get it:
<url>
<url>
Cheers,
Udo
_______________________________________________
vdr mailing list
<email_address>
<url>"
    @KlausSchmidinger: "<quote>
Is this fix also relevant for the original VDR 1.7.0?
BTW: just curious, but what exactly is the reason for this "API wrapper"?
Shouldn't we rather encourage people to switch to the multiproto driver?
After all, I did release a stable version 1.6 for those who don't want to
(or can't) switch to the multiproto driver. Now we're at a new *developer*
version, which should *focus* on making the switch to multiproto.
Just my thoughts, no offense intended, and of course it's your decision
to maintain such a patch ;-)
Klaus
_______________________________________________
vdr mailing list
<email_address>
<url>"
    @udo_richter: "<quote>
No, its just a wrapper bug: After importing a DVB-S channels.conf from 
1.6.0, VDR uses DVBFE_MOD_AUTO as modulation, and after the next channel 
update, VDR uses DVBFE_MOD_QPSK. Previous versions of the patch did not 
accept AUTO.
VDR 1.7 can (and will) enforce the multiproto development, and thats ok. 
The DVB-S2 movement alone will make sure that multiproto won't get stuck 
for long.
I made the patch mainly for personal reasons: I'm running a VDR binary 
currently on 4 different systems, a 5'th is in planning. I'm not really 
interested in building kernels and drivers for all of them, and probably 
having to update these often too. (One is a Knoppix base, replacing the 
kernel wouldn't even be easy.)
Also, I'm not sure what will happen first: All distributions using stock 
kernels with multiproto support by default, or VDR 1.8.0 being ready. In 
the end, it might be necessary to have fallback support anyway, at least 
for distribution packages. And wrapping these few ioctl calls isn't that 
difficult.
Cheers,
Udo
_______________________________________________
vdr mailing list
<email_address>
<url>"
    @halimsahin: "Hi,
Thanks Udo for this patch.
The threadstarter can resend his message if multiproto driver is merged
to official linux kernel and linux-dvb.
Currently this patch is really useful.
Regards.
Halim
_______________________________________________
vdr mailing list
<email_address>
<url>"
    @udo_richter: "<quote>
I think that there's a need for it. In my opinion something like VDR 
should work on any stable Linux distribution without requiring special 
kernels and drivers to be installed. I know that the goal is to push 
multiproto development, but intentionally forcing incompatibility to 
enforce people to upgrade their systems is not really typical for open 
source OSes, is it?
Lets do some optimistic timeline estimations: Multiproto is currently a 
fork of the off-kernel DVB drivers. Lets assume another half year til 
this is part of the main DVB drivers. Another half year to get it into 
stable kernels. This will surely be too late for Debain/Lenny for 
example, and VDR will not run on native Debian/Stable before around 
2011. This also means no more official Debian VDR packages newer than 
VDR 1.6.x until then.
Driver development will be pushed anyway, as DVB-S2 users need them. And 
there will be lots of them soon. But why force frequent kernel and 
driver updates to DVB-S/C/T users and even pure streaming clients, if 
they don't really need them?
VDR and plugins continue to evolve to multiproto anyway, the wrapper 
doesn't turn back time: VDR continues to internally use multiproto, the 
wrapper provides a 'fake' multiproto driver. And the new runtime 
detecting even allows transition: Just use the normal VDR binary package 
together with new drivers, and S2 works right out of the box! Fully 
support bleeding edge technology without spoiling old users! There's no 
way to make the switch to HD any easier than that.
Cheers,
Udo
PS: 151 downloads of API wrapper 0.3, and 19 downloads of API wrapper 
0.4 in the last 15 -mostly night- hours. No need for it?
_______________________________________________
vdr mailing list
<email_address>
<url>"
    @uservdr: "This patch will NOT prevent development of multiproto!  DVB-S2 is here
to stay and it is only being developed for multiproto.  As well I've
heard the kernel maintainers want multiproto asap.  In the meantime
there are some drivers which exist in v4l that people still need.  I
personally have a mixture of cards.  Some need v4l, some need
multiproto, some can use either tree.  I appreciate the wrapper as
I've been told directly that some drivers will not be updated for
multiproto until multiproto is fully adopted!
_______________________________________________
vdr mailing list
<email_address>
<url>"
{'source': 'USENET', 'other_information': '{"reply_count": 5, "forum_name": "boerde.lists.vdr.20140612.mbox"}', 'file': 'data/output/usenet-boerde.lists.parquet'}