I was wondering what the people on the VDR ml thought about this.
Now that multiproto is finally complete, and VDR has excellent support for it, some people want to create a completely new API. They say this is so that future modulations could be better supported, but multiproto can offer that support, too, with not much effort and without breaking compatibility.
Overall, the call for this new API seems like something personal between the developers, but I'm on slippery ice here.
It seems stupid that the users would have to pay for some fight by having to wait another few months for this new API to get completed.
/Met vriendelijke groeten,/
*Jelle De Loecker* Kipdola Studios - Tomberg
Goga777 schreef:
http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Thu, Sep 4, 2008 at 12:28 PM, Jelle De Loecker skerit@kipdola.com wrote:
I was wondering what the people on the VDR ml thought about this.
Now that multiproto is finally complete, and VDR has excellent support for it, some people want to create a completely new API. They say this is so that future modulations could be better supported, but multiproto can offer that support, too, with not much effort and without breaking compatibility.
Overall, the call for this new API seems like something personal between the developers, but I'm on slippery ice here.
It seems stupid that the users would have to pay for some fight by having to wait another few months for this new API to get completed.
Unfortunately personal politics has a lot to do with it even though it's not admitted in open public. It's no coincidence that the person delaying the multiproto pull request is also one of the main guys for the new api. Additionally, there's a long history of "disagreements" between the parties involved. There has even been attempts to mislead people about multiproto in an effort to gain support for the new api. The more I look into this, the more childishness I discover taking place.
Jelle De Loecker wrote:
I was wondering what the people on the VDR ml thought about this.
From a non-dvb-insider perspective who doesn't really need things like s2 right now, I'm seeing this form a relaxed point of view.
The two APIs seem to do things different, but in the end they both offer the same. The multiproto is more like a redesigned version of the old API, the S2API seems a bit more flexible and generic. For userspace applications, things are probably not too different to do.
I cannot comment on the driver's internal structures, and how easy/difficult it is to write drivers for them and how difficult/easy it is to keep compatibility with existing apps/drivers, but this seems to be one part of the discussion too.
In the end, some competition is never wrong, and time will show which concept will win. At least the last 10 days have seen a lot more activity in the future DVB drivers, than in the months before that.
Cheers,
Udo
-
Goga777 -
Jelle De Loecker -
Udo Richter -
VDR User