From: Bob W <bob.news@non-elite.com>
To: Konstantin Dimitrov <kosio.dimitrov@gmail.com>
Cc: linux-media@vger.kernel.org,
"Christian Prähauser" <cpraehaus@cosy.sbg.ac.at>
Subject: Re: DVB-S2 multistream support
Date: Tue, 13 Mar 2012 10:47:57 -0500 [thread overview]
Message-ID: <4F5F6C2D.1080206@non-elite.com> (raw)
In-Reply-To: <CAF0Ff2n1wj5LTu935sR6jxYP8ncHHEA=f6urs8+QKcD2Zd04zg@mail.gmail.com>
Hi Konstantin,
> all work to support BBFrames in the Linux kernel is done by Christian
> - in fact it's a long lost work from 5 years ago:
>
> http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022217.html
yep, I have followed the history back... and like Christian said, the
old repo is nolonger working. :(
>
> and i hope it won't be lost again. i just encouraged Christian that
> his work is important and there are people interested in it - you're
> one such example. so, i offered Christian to help him with i can. i
> guess more people appreciating what his doing and encourage him will
> give him better motivation to release the code to the public. however,
> i guess the delay is more, because it's not easy and it requires time
> to prepare the code for initial public release and that's why the
> delay. so, i don't have Christian's code and i'm eager as you're to be
> able to try it out, but we need to be patient. i'm sure that after
> there is some public release and repository more people will be
> interested to contribute to that work.
>
> best regards,
> konstantin
Agreed, I understand the pressure of releasing publicly. Once released,
the nit picking begins.. lol. I will keep watch on the list.
Christian, if you want an extra tester to help yah, count me in. I'll
help also with what I can.
Bob
next prev parent reply other threads:[~2012-03-13 15:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 1:06 DVB-S2 multistream support Georgi Chorbadzhiyski
2011-12-25 8:23 ` Antti Palosaari
2011-12-25 10:17 ` Mauro Carvalho Chehab
2011-12-25 10:55 ` Konstantin Dimitrov
2011-12-25 11:18 ` Mauro Carvalho Chehab
2011-12-25 12:37 ` Konstantin Dimitrov
2011-12-27 10:12 ` Christian Prähauser
2011-12-27 16:08 ` Antti Palosaari
2012-01-19 13:34 ` Marek Ochaba
2012-01-21 10:29 ` Christian Prähauser
2012-01-23 13:58 ` Marek Ochaba
2012-01-22 2:13 ` Mauro Carvalho Chehab
2012-01-22 12:44 ` Christian Prähauser
[not found] ` <CAF0Ff2mf0tYs3UG3M6Cahep+_kMToVaGgPhTqR7zhRG0UXWuig@mail.gmail.com>
[not found] ` <85A7A8FC-150C-4463-B09C-85EED6F851A8@cosy.sbg.ac.at>
[not found] ` <CAF0Ff2ncv0PJWSOOw=7WeGyqX3kKiQitY52uEOztfC8Bwj6LgQ@mail.gmail.com>
2012-01-25 13:12 ` Christian Prähauser
2012-02-01 18:49 ` Konstantin Dimitrov
2012-02-18 19:06 ` Christian Prähauser
2012-02-19 23:12 ` Konstantin Dimitrov
2012-03-07 16:33 ` Bob Winslow
2012-03-13 9:36 ` Marek Ochaba
2012-03-13 12:30 ` Bob W
2012-03-13 15:22 ` Konstantin Dimitrov
2012-03-13 15:47 ` Bob W [this message]
2012-03-15 9:40 ` Christian Prähauser
2012-03-19 8:46 ` Christian Prähauser
2012-03-19 15:19 ` Konstantin Dimitrov
2012-04-24 22:18 ` Bob W
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=4F5F6C2D.1080206@non-elite.com \
--to=bob.news@non-elite.com \
--cc=cpraehaus@cosy.sbg.ac.at \
--cc=kosio.dimitrov@gmail.com \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).