From: Christophe Thommeret <hftom@free.fr>
To: linux-dvb@linuxtv.org
Cc: Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [linux-dvb] S2API vs Multiproto vs TT 3200
Date: Tue, 7 Oct 2008 20:52:11 +0200 [thread overview]
Message-ID: <200810072052.12369.hftom@free.fr> (raw)
In-Reply-To: <48EB956D.9010900@gmail.com>
Le Tuesday 07 October 2008 18:59:25 Manu Abraham, vous avez écrit :
> I do plan to have a port of the STB0899 + STV090x.
Hi Manu,
That's good news.
> The reason why i do
> say a port and still maintain multiproto:
Well, I really hope you won't join Markus desperate way of breaking Linux DVB
community.
> S2API is incapable of handling
> DVB-S2 ACM (with 16/32APSK) as it is, ie, doesn't support DVBFE_GET_INFO
> for notification of MODCOD changes.
>
> Similar to a patch that i had posted for handling diversity some days?
> back.
>
> With regards to the cx24116, this is of no concern as it doesn't support
> 16/32APSK in any event.
>
> Or is there any bugfix to S2API which updates the DVBFE_GET_EVENT ioctl ?
S2API is now merged and thus is given to the whole community. And YOU are part
of this community, so the new API is yours also. If you want to submit
fixes/patches, you have of course the rights to do so, and if it's a good one
(and i'm pretty sure it will) i will second it for adoption.
Best Regards, Manu.
--
Christophe Thommeret
_______________________________________________
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-10-07 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 12:40 [linux-dvb] S2API vs Multiproto vs TT 3200 gimli
2008-10-07 12:48 ` Jaap Crezee
2008-10-07 14:06 ` Gregoire Favre
2008-10-07 15:07 ` Steven Toth
2008-10-07 16:59 ` Manu Abraham
2008-10-07 18:52 ` Christophe Thommeret [this message]
2008-10-07 20:48 ` hermann pitton
2008-10-07 14:31 ` Igor M. Liplianin
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=200810072052.12369.hftom@free.fr \
--to=hftom@free.fr \
--cc=abraham.manu@gmail.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