From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-media@vger.kernel.org
Subject: Re: [PATCH] Add FE_CAN_TURBO_FEC (was: Add FE_CAN_PSK_8 to allow apps to identify PSK_8 capable DVB devices)
Date: Sun, 02 May 2010 11:34:20 +0200 [thread overview]
Message-ID: <4BDD471C.5020401@cadsoft.de> (raw)
In-Reply-To: <j2g1a297b361004181245redcf8a69odd957f583404b158@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Some (North American) providers use a non-standard mode called
"8psk turbo fec". Since there is no flag in the driver that
would allow an application to determine whether a particular
device can handle "turbo fec", the attached patch introduces
FE_CAN_TURBO_FEC.
Since there is no flag in the SI data that would indicate
that a transponder uses "turbo fec", VDR will assume that
all 8psk transponders on DVB-S use "turbo fec".
Signed-off-by: Klaus Schmidinger <Klaus.Schmidinger@tvdr.de>
Tested-by: Derek Kelly <user.vdr@gmail.com>
[-- Attachment #2: v4l-dvb-add-FE_CAN_TURBO_FEC.diff --]
[-- Type: text/x-patch, Size: 1137 bytes --]
--- linux/include/linux/dvb/frontend.h.001 2010-04-05 16:13:08.000000000 +0200
+++ linux/include/linux/dvb/frontend.h 2010-04-25 14:24:50.000000000 +0200
@@ -62,6 +62,7 @@
FE_CAN_8VSB = 0x200000,
FE_CAN_16VSB = 0x400000,
FE_HAS_EXTENDED_CAPS = 0x800000, /* We need more bitspace for newer APIs, indicate this. */
+ FE_CAN_TURBO_FEC = 0x8000000, /* frontend supports "turbo fec modulation" */
FE_CAN_2G_MODULATION = 0x10000000, /* frontend supports "2nd generation modulation" (DVB-S2) */
FE_NEEDS_BENDING = 0x20000000, /* not supported anymore, don't use (frontend requires frequency bending) */
FE_CAN_RECOVER = 0x40000000, /* frontend can recover from a cable unplug automatically */
--- linux/drivers/media/dvb/dvb-usb/gp8psk-fe.c.001 2010-04-05 16:13:08.000000000 +0200
+++ linux/drivers/media/dvb/dvb-usb/gp8psk-fe.c 2010-04-25 14:25:18.000000000 +0200
@@ -349,7 +349,7 @@
* FE_CAN_QAM_16 is for compatibility
* (Myth incorrectly detects Turbo-QPSK as plain QAM-16)
*/
- FE_CAN_QPSK | FE_CAN_QAM_16
+ FE_CAN_QPSK | FE_CAN_QAM_16 | FE_CAN_TURBO_FEC
},
.release = gp8psk_fe_release,
prev parent reply other threads:[~2010-05-02 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 9:12 [PATCH] Add FE_CAN_PSK_8 to allow apps to identify PSK_8 capable DVB devices Klaus Schmidinger
2010-04-15 20:21 ` Manu Abraham
2010-04-18 13:19 ` [linux-media] " Klaus Schmidinger
2010-04-18 14:51 ` Manu Abraham
2010-04-18 18:34 ` [linux-media] " Klaus Schmidinger
2010-04-18 19:45 ` Manu Abraham
2010-05-02 9:34 ` Klaus Schmidinger [this message]
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=4BDD471C.5020401@cadsoft.de \
--to=klaus.schmidinger@cadsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox