From: Jelle De Loecker <skerit@kipdola.com>
To: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] DVB-S2 / Multiproto and future modulation support
Date: Mon, 01 Sep 2008 19:24:10 +0200 [thread overview]
Message-ID: <48BC253A.7050409@kipdola.com> (raw)
In-Reply-To: <a3ef07920809010938h22f71abfgb633ba9f06c2d41e@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2039 bytes --]
You said everything that needed to be said, I agree with you 100 %
I vote for the merging of multiproto.
/Met vriendelijke groeten,/
*Jelle De Loecker*
Kipdola Studios - Tomberg
VDR User schreef:
> After some consideration, I can not ack this new api proposal. I
> believe a lot of the support for it is based in people not knowing the
> current state of multiproto and thinking this might be the only path
> to new needed drivers. It hasn't helped that there has been some
> misinformation spread such as the binary compatibility and so on.
> There is a current pull request for multiproto right now and if done,
> drivers could start being developed right now. In the end that's what
> matters to users, especially those of us who've been patiently waiting
> several months or even years.
>
> To my knowledge the multiproto api is very robust and can be easily
> updated to accommodate new modulations, etc. From a technical
> standpoint, I can't justify disregarding all the work thats been done
> on multiproto, especially when it's finally ready to go. In Mauro's
> own response to the pull request, he admits the multiproto code is
> complete. Unless someone can provide legitimate reasons why we should
> wait for yet another api to be written when multiproto is (finally)
> ready to be pulled now, I'm afraid I can't support the idea.
>
> People have been waiting to move forward with a new api for a long
> time and it seems we can with multiproto right now, today. I don't
> agree that makes a very strong case of too little, too late. Whether
> it's openly admitted or not, I think we're mostly all aware that there
> is some personal politics involved in this as well, which is
> unfortunate. Hopefully people will be mature enough to put that aside
> and do what's best for us, the linux dvb user base, as a whole. After
> learning that multiproto is ready and there's no technical reason
> against it, I wonder how many people still choose to wait for another
> api to be written..?
>
> Best regards guys!
>
[-- Attachment #1.2: Type: text/html, Size: 2444 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-01 17:24 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 21:05 [linux-dvb] DVB-S2 / Multiproto and future modulation support Igor M. Liplianin
2008-08-31 21:40 ` Steven Toth
2008-09-01 16:38 ` VDR User
2008-09-01 17:24 ` Jelle De Loecker [this message]
2008-09-01 20:28 ` Mauro Carvalho Chehab
2008-09-01 22:27 ` [linux-dvb] Re : " manu
2008-09-01 20:34 ` [linux-dvb] " Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2008-08-29 18:29 Steven Toth
2008-08-29 19:00 ` Hans Werner
2008-08-29 19:20 ` P. van Gaans
2008-08-29 21:05 ` Grégoire FAVRE
2008-08-30 16:03 ` Udo Richter
2008-08-30 0:04 ` Christophe Thommeret
2008-08-30 0:37 ` Steven Toth
2008-08-30 11:16 ` Oliver Endriss
2008-08-30 14:48 ` Steven Toth
2008-08-30 11:16 ` Christian Tramnitz
2008-08-30 14:51 ` Steven Toth
2008-08-30 12:16 ` ChaosMedia > WebDev
2008-08-30 14:57 ` Steven Toth
2008-08-30 14:16 ` Andreas Oberritter
2008-08-30 15:00 ` Steven Toth
2008-08-30 15:08 ` Artem Makhutov
2008-08-30 15:14 ` Steven Toth
2008-08-30 16:06 ` Goga777
2008-08-30 17:39 ` Steven Toth
2008-08-30 16:58 ` Manu Abraham
2008-08-30 17:05 ` Manu Abraham
2008-08-30 15:30 ` Janne Grunau
2008-08-30 17:26 ` Steven Toth
2008-08-30 16:59 ` Douglas Schilling Landgraf
2008-08-30 17:27 ` Steven Toth
2008-08-30 17:03 ` Nicolas Will
2008-08-30 17:29 ` Steven Toth
2008-08-30 17:53 ` Charles Price
2008-08-30 18:03 ` Steven Toth
2008-08-31 3:57 ` Markus Rechberger
2008-08-31 10:32 ` Michael J. Curtis
2008-08-31 21:26 ` Steven Toth
[not found] ` <20080831042115.GA21622@kroah.com>
2008-09-05 20:54 ` Aidan Thornton
2008-08-31 14:58 ` Jan Hoogenraad
[not found] ` <48BAAEC1.5070105@h-i-s.nl>
2008-08-31 21:37 ` Steven Toth
2008-09-01 20:35 ` Hans Verkuil
2008-09-04 14:25 ` Steven Toth
[not found] ` <200809101340.09702.hftom@free.fr>
[not found] ` <48C7CDCF.9090300@hauppauge.com>
2008-09-10 15:10 ` Christophe Thommeret
2008-09-10 15:33 ` Janne Grunau
2008-09-10 18:39 ` Steven Toth
2008-09-10 22:46 ` hermann pitton
2008-09-10 16:12 ` Hans Werner
2008-09-10 18:47 ` Steven Toth
2008-09-10 22:59 ` Andreas Oberritter
2008-09-11 0:01 ` Christophe Thommeret
2008-09-11 1:00 ` Steven Toth
2008-09-11 1:17 ` hermann pitton
2008-09-11 2:59 ` Steven Toth
2008-09-11 4:10 ` hermann pitton
2008-09-11 12:51 ` Steven Toth
2008-09-11 21:08 ` hermann pitton
2008-09-11 4:22 ` Andreas Oberritter
2008-09-11 5:44 ` Uri Shkolnik
2008-09-11 13:43 ` barry bouwsma
2008-09-11 15:06 ` Andreas Oberritter
2008-09-11 5:48 ` Uri Shkolnik
2008-09-10 18:32 ` Steven Toth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BC253A.7050409@kipdola.com \
--to=skerit@kipdola.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox