From: "P. van Gaans" <w3ird_n3rd@gmx.net>
To: VDR User <user.vdr@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Merge multiproto tree
Date: Mon, 01 Sep 2008 18:23:39 +0200 [thread overview]
Message-ID: <48BC170B.9040805@gmx.net> (raw)
In-Reply-To: <a3ef07920809010900l5f4bde4buaac6bcf38e9c034e@mail.gmail.com>
On 09/01/2008 06:00 PM, VDR User wrote:
> On Mon, Sep 1, 2008 at 8:06 AM, Mauro Carvalho Chehab
> <mchehab@infradead.org> wrote:
>> I'm aware that your solution seems to be more code-complete than Steven's
>> proposal.
>>
>> But the recent activity on the mailing list regarding his idea (and its,
>> so far, positive feedback) and the fact that I was anyway planning to
>> have a discussion about the future of the DVB-API at the Linux Plumbers
>> Conference 2008 are supporting me in my idea of post-poning such a pull to
>> a point in time shortly after this event.
>
> I understand peoples frustration in waiting for multiproto since I'm
> one of them as well. However, I believe the support for Steven's
> proposal is largely because people aren't aware that multiproto is now
> in a ready-state and has a pull request pending. Over the last
> several months I've seen many question when/if multiproto will be
> done, or if it is dead... I think we all agree that it has taken
> quite some time for multiproto to get to a point where it's ready but
> that time has come.
>
> Multiproto -can- be pulled in right now, and if that happened, drivers
> could be written immediately, finally providing users with what
> they've needed for so long. In my opinion it makes no sense to throw
> out a robust api that is ready right now just because of frustration
> and past personal grudges (whether anyone will openly admit to this or
> not, it -is- a part of this). The questions for consideration -should
> be-... Is the code ready? Can it handle future specs? Is it missing
> anything that should be included? If the code is ready and is robust,
> then the final question is what benefit is there in making people wait
> yet longer for another api to be written? Will this new api proposal
> offer anything that multiproto doesn't already?
>
> It seems we can finally move forward and now instead of incomplete
> code stopping it, politics are.
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
If what VDR User and Jelle De Loecker are saying is right, I don't see a
reason for not going with multiproto either.
I'm an enduser and I would be happy with multiproto as well. I think I'm
not alone if I say I care less *what* the solution is going to be, as
long as we get DVB-S2 support in-kernel.
P. van Gaans
_______________________________________________
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 16:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 11:59 Merge multiproto tree Manu Abraham
2008-08-30 12:24 ` Peter Zijlstra
2008-08-30 12:26 ` Willy Tarreau
2008-08-30 12:40 ` Peter Zijlstra
2008-09-01 1:08 ` [v4l-dvb-maintainer] " hermann pitton
2008-09-01 4:08 ` Peter Zijlstra
2008-09-02 0:16 ` hermann pitton
2008-08-30 15:27 ` [linux-dvb] " Grégoire FAVRE
2008-09-01 15:06 ` Mauro Carvalho Chehab
2008-09-01 15:06 ` [linux-dvb] " Mauro Carvalho Chehab
2008-09-01 15:55 ` Jelle De Loecker
2008-09-01 16:00 ` VDR User
2008-09-01 16:23 ` P. van Gaans [this message]
2008-09-01 16:22 ` Marcel Siegert
2008-09-01 21:14 ` Mauro Carvalho Chehab
[not found] ` <48D75194.6090006@linuxtv.org>
[not found] ` <a3ef07920809220728wf544c2cg58035826bb436de6@mail.gmail.com>
2008-09-22 16:20 ` Simon Kenyon
2008-09-01 20:33 ` Manu Abraham
2008-09-01 20:48 ` [linux-dvb] " Christophe Thommeret
2008-09-01 21:06 ` Manu Abraham
2008-09-01 21:09 ` Jelle De Loecker
2008-09-01 22:58 ` Christophe Thommeret
2008-09-01 18:33 ` Hans Werner
2008-09-01 20:23 ` Manu Abraham
-- strict thread matches above, loose matches on Subject: below --
2008-09-01 16:52 lucian orasanu
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=48BC170B.9040805@gmx.net \
--to=w3ird_n3rd@gmx.net \
--cc=linux-dvb@linuxtv.org \
--cc=user.vdr@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.