From: Steven Toth <stoth@linuxtv.org>
To: "Igor M. Liplianin" <liplianin@tut.by>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVB-S2 / Multiproto and future modulation support
Date: Sun, 31 Aug 2008 17:40:55 -0400 [thread overview]
Message-ID: <48BB0FE7.2010109@linuxtv.org> (raw)
In-Reply-To: <200809010005.28716.liplianin@tut.by>
Igor M. Liplianin wrote:
> В сообщении от 29 August 2008 21:29:30 Steven Toth написал(а):
>> Regarding the multiproto situation:
>>
>> A number of developers, maintainers and users are unhappy with the
>> multiproto situation, actually they've been unhappy for a considerable
>> amount of time. The linuxtv developer community (to some degree) is seen
>> as a joke and a bunch in-fighting people. Multiproto is a great
>> demonstration of this. [1] The multiproto project has gone too far, for
>> too long and no longer has any credibility in the eyes of many people.
>>
>> In response, a number developers have agreed that "enough is enough" and
>> "it's time to take a new direction", for these developers the technical,
>> political and personal cost of multiproto is too high. These developers
>> have decided to make an announcement.
>>
>> Mauro Chehab, Michael Krufky, Patrick Boettcher and myself are hereby
>> announcing that we no longer support multiproto and are forming a
>> smaller dedicated project group which is focusing on adding next
>> generation S2/ISDB-T/DVB-H/DVB-T2/DVB-SH support to the kernel through a
>> different and simpler API.
>>
>> Basic patches and demo code for this API is currently available here.
>>
>> http://www.steventoth.net/linux/s2
>>
>> Does it even work? Yes
>> Is this new API complete? No
>> Is it perfect? No, we've already had feedback on structural and
>> namingspace changes that people would like to see.
>> Does it have bugs? Of course, we have a list of things we already know
>> we want to fix.
>>
>> but ...
>>
>> Is the new approach flexible? Yes, we're moving away from passing fixed
>> modulation structures into the kernel.
>> Can we add to it without breaking the future ABI when unforseen
>> modulations types occur? Yes
>> Does it preserve backwards compatibility? Yes
>> Importantly, is the overall direction correct? Yes
>> Does it impact existing frontend drivers? No.
>> What's the impact to dvb-core? Small.
>> What's the impact to application developers? None, unless an application
>> developer wants to support the new standards - binary compatibility!
>>
>> We want feedback and we want progress, we aim to achieve it.
>>
>> Importantly, this project group seeks your support.
>>
>> If you also feel frustrated by the multiproto situation and agree in
>> principle with this new approach, and the overall direction of the API
>> changes, then we welcome you and ask you to help us.
>>
>> Growing the list of supporting names by 100%, and allowing us to publish
>> your name on the public mailing list, would show the non-maintainer
>> development community that we recognize the problem and we're taking
>> steps to correct the problem. We want to make LinuxTV a perfect platform
>> for S2, ISDB-T and other advanced modulation types, without using the
>> multiproto patches.
>>
>> We're not asking you for technical help, although we'd like that :) ,
>> we're just asking for your encouragement to move away from multiproto.
>>
>> If you feel that you want to support our movement then please help us by
>> acking this email.
>>
>> Regards - Steve, Mike, Patrick and Mauro.
>>
>> Acked-by: Patrick Boettcher <pb@linuxtv.org>
>> Acked-by: Michael Krufky <mkrufky@linuxtv.org>
>> Acked-by: Steven Toth <stoth@linuxtv.org>
>> Acked-by: Mauro Carvalho Chehab <mchehab@infradead.org>
>>
>> * [1]. Rather than point out the issues with multiproto here, take a
>> look at the patches and/or read the comments on the mailing lists.
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> I am not much a letter writer.
> So one way or another, DVB-S2 needs to be included.
> Who makes first technical step? I mean working S2 driver in v4l-dvb tree.
> I truly want to see that!
>
> I see the problem like that - I have a card, I want it to work under Linux,
> I don't see any reasons to wait for someone to make a driver (it is lasting
> for years, you know), I make it myself. Any political reasons?
Is this the HVR4000 driver that I wrote in 2006 (still not in the
kernel)? I feel your pain.
Thanks for your feedback Igor.
Regards,
Steve
_______________________________________________
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-08-31 21:41 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 [this message]
2008-09-01 16:38 ` VDR User
2008-09-01 17:24 ` Jelle De Loecker
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=48BB0FE7.2010109@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=linux-dvb@linuxtv.org \
--cc=liplianin@tut.by \
/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