All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Schmidinger <Klaus.Schmidinger@tvdr.de>
To: linux-media@vger.kernel.org
Subject: Re: [linux-media] Re: [git:v4l-dvb/master] V4L/DVB: Add FE_CAN_PSK_8 to allow apps to	identify PSK_8 capable DVB devices
Date: Wed, 21 Apr 2010 10:46:08 +0200	[thread overview]
Message-ID: <4BCEBB50.6040105@tvdr.de> (raw)
In-Reply-To: <4BCEB022.2040807@linuxtv.org>

On 04/21/10 09:58, Andreas Oberritter wrote:
> Hello Mauro,
> 
> Mauro Carvalho Chehab wrote:
>> Subject: V4L/DVB: Add FE_CAN_PSK_8 to allow apps to identify PSK_8 capable DVB devices
>> Author:  Klaus Schmidinger <Klaus.Schmidinger@tvdr.de>
>> Date:    Sun Apr 11 06:12:52 2010 -0300
> 
> I wonder why this patch was applied without any modification. It seems
> like, as Manu pointed out, the flag should really indicate support for
> Turbo-FEC modes rather than just 8PSK (which is already a subset of
> FE_CAN_2G_MODULATION).
> 
> Btw., there is also no FE_CAN_APSK_16, FE_CAN_APSK_32 or FE_CAN_DQPSK.
> 
> Also, I'm unsure how to instruct a driver whether to choose Turbo-FEC
> mode or not in case it supports both DVB-S2 and what's used in the US.
> 
> Third, it was stated that cx24116's support for Turbo-FEC was untested
> and probably unsupported.
> 
> So I'd vote for reverting this patch until these issues are cleared.
> 
> If my assumptions above are correct, my proposal is to rename the flag
>  to FE_CAN_TURBO_FEC (as Manu proposed earlier) and remove it from
> cx24116.c.

That's what I was intending to do - time permitting ;-)
I was also surprised that the patch got applied, since I was in the
middle of discussing this with Manu...

Klaus

  reply	other threads:[~2010-04-21  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1O4Rsq-0006zj-NH@www.linuxtv.org>
2010-04-21  7:58 ` [git:v4l-dvb/master] V4L/DVB: Add FE_CAN_PSK_8 to allow apps to identify PSK_8 capable DVB devices Andreas Oberritter
2010-04-21  8:46   ` Klaus Schmidinger [this message]
2010-04-21 14:34   ` Mauro Carvalho Chehab

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=4BCEBB50.6040105@tvdr.de \
    --to=klaus.schmidinger@tvdr.de \
    --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 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.