From: Bob Goddard <linuxtv@1.linuxtv.bgcomp.co.uk>
To: linux-media@vger.kernel.org
Subject: Errors in scan file
Date: Tue, 26 Apr 2016 12:34:29 +0100 [thread overview]
Message-ID: <1468342.S21sjePQjL@eth7> (raw)
I posted an email with a patch back on 04/02/2016 17:32 only to find that nothing has been done.
This patch, reproduced below adds 2 new transponders to Astra 28.2E and removes a trailing space. This trailing spaces causes dvbv5-scan to segfault.
Why has this not been actioned and why was my email address banned? Is this a close community that tells people to f-off?
dvb-s/Astra-28.2E | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/dvb-s/Astra-28.2E b/dvb-s/Astra-28.2E
index ea06c56..42168f6 100644
--- a/dvb-s/Astra-28.2E
+++ b/dvb-s/Astra-28.2E
@@ -264,6 +264,17 @@
MODULATION = QPSK
INVERSION = AUTO
+## Astra 2E
+# Transponder 31
+[CHANNEL]
+ DELIVERY_SYSTEM = DVBS
+ FREQUENCY = 12304000
+ POLARIZATION = HORIZONTAL
+ SYMBOL_RATE = 27500000
+ INNER_FEC = 2/3
+ MODULATION = QPSK
+ INVERSION = AUTO
+
# Transponder 32
[CHANNEL]
DELIVERY_SYSTEM = DVBS2
@@ -572,7 +583,7 @@
[CHANNEL]
DELIVERY_SYSTEM = DVBS
FREQUENCY = 11170750
- POLARIZATION = HORIZONTAL
+ POLARIZATION = HORIZONTAL
SYMBOL_RATE = 22000000
INNER_FEC = 5/6
MODULATION = QPSK
@@ -611,8 +622,8 @@
# Transponder 93
[CHANNEL]
DELIVERY_SYSTEM = DVBS
- FREQUENCY = 11508500
- POLARIZATION = VERTICAL
+ FREQUENCY = 11523500
+ POLARIZATION = HORIZONTAL
SYMBOL_RATE = 22000000
INNER_FEC = 5/6
MODULATION = QPSK
@@ -678,6 +689,16 @@
MODULATION = PSK/8
INVERSION = AUTO
+# Transponder 102
+[CHANNEL]
+ DELIVERY_SYSTEM = DVBS
+ FREQUENCY = 11656000
+ POLARIZATION = VERTICAL
+ SYMBOL_RATE = 22000000
+ INNER_FEC = 5/6
+ MODULATION = QPSK
+ INVERSION = AUTO
+
# Transponder 103
[CHANNEL]
DELIVERY_SYSTEM = DVBS
reply other threads:[~2016-04-26 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1468342.S21sjePQjL@eth7 \
--to=linuxtv@1.linuxtv.bgcomp.co.uk \
--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