From: Jelle De Loecker <skerit@kipdola.com>
To: Hans Werner <HWerner4@gmx.de>,
v4l-dvb-maintainer@linuxtv.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Future of DVB-S2
Date: Thu, 28 Aug 2008 23:22:14 +0200 [thread overview]
Message-ID: <48B71706.3000504@kipdola.com> (raw)
In-Reply-To: <20080823200531.246370@gmx.net>
[-- Attachment #1.1: Type: text/plain, Size: 1692 bytes --]
Yet all we need is some clarification on what's going to happen in the
future.
/Met vriendelijke groeten,/
*Jelle De Loecker*
Kipdola Studios - Tomberg
Hans Werner schreef:
>> An: linux-dvb@linuxtv.org, mchehab@infradead.org, v4l-dvb-maintainer@linuxtv.org
>> Betreff: [linux-dvb] Future of DVB-S2
>>
>
>
>> A question to the maintainer:
>>
>> what is your plan for getting DVB-S2 support into the mainline kernel?
>>
>> So many people have put so much time and effort into creating a working
>> API, drivers
>> and applications but I have seen no indications of the direction and
>> timescale anywhere.
>>
>> All this work is of very little value if it does not end up in the
>> mainline kernel. Maintaining
>> out-of-kernel projects and patches over the long term is a terrible waste
>> of effort for
>> maintainers, developers and experienced users. It also makes Linux DVB
>> look less than
>> professional, and is almost worthless to most end users.
>>
>> Working code already exists but it needs to be managed into a form that
>> can be merged
>> with the kernel.
>>
>> So how is it going to be done? It's really not that hard.
>>
>
> Bump.
>
> It's disappointingly silent so far....
>
> In the interest of making progress I will be more specific.
>
> It is easily possible to use the work that has already been done to quickly create (and debug
> and merge) kernel patches which will provide support for one or more DVB-S2 cards.
>
> But before such patches can be created, there needs to be a clear statement about
> which API changes (if any) will be permitted.
>
> How will the API change? Who is going to make the decision? When?
>
> Hopefully,
> Hans
>
>
[-- Attachment #1.2: Type: text/html, Size: 2400 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 parent reply other threads:[~2008-08-28 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080821173909.114260@gmx.net>
[not found] ` <20080823200531.246370@gmx.net>
2008-08-28 21:22 ` Jelle De Loecker [this message]
2008-08-29 5:36 ` [linux-dvb] Future of DVB-S2 P. van Gaans
2008-08-29 7:32 ` Jelle De Loecker
2008-08-29 14:08 ` Steven Toth
2008-08-29 15:43 ` [linux-dvb] [PATCH] " Hans Werner
2008-08-29 15:52 ` Michael Krufky
2008-08-29 16:03 ` Steven Toth
2008-08-29 18:26 ` Hans Werner
2008-08-29 18:34 ` Steven Toth
2008-08-29 16:43 ` Hans Werner
2008-08-29 16:50 ` Jelle De Loecker
2008-08-29 17:11 ` Hans Werner
2008-08-29 17:52 ` Steven Toth
2008-08-29 18:52 ` Oliver Endriss
2008-08-29 19:15 ` Manu Abraham
2008-08-29 23:46 ` Jelle De Loecker
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=48B71706.3000504@kipdola.com \
--to=skerit@kipdola.com \
--cc=HWerner4@gmx.de \
--cc=linux-dvb@linuxtv.org \
--cc=v4l-dvb-maintainer@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 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.