From: Richard F <lists@keynet-technology.com>
To: linux-media@vger.kernel.org
Subject: dtv_property_legacy_params_sync
Date: Fri, 02 Jan 2015 19:10:51 +0000 [thread overview]
Message-ID: <54A6ED3B.9020004@keynet-technology.com> (raw)
dtv_property_legacy_params_sync: doesn't know how to handle a DVBv3 call to delivery system 0
Hi,
I'm new to this list, just updated VDR (2.06) and a newer kernel (3.12)
and getting
the above messages from my dtt200u receiver fill my kernel log.
Is there a straightforward way to stop them?
The suggestion from the VDR list is that this is a driver issue.
dvb-fe-tool gives the following output but can't set the V5 delivery
system for some reason.
Thanks
INFO Device WideView USB DVB-T (/dev/dvb/adapter0/frontend0) capabilities:
INFO CAN_FEC_1_2
INFO CAN_FEC_2_3
INFO CAN_FEC_3_4
INFO CAN_FEC_5_6
INFO CAN_FEC_7_8
INFO CAN_FEC_AUTO
INFO CAN_GUARD_INTERVAL_AUTO
INFO CAN_HIERARCHY_AUTO
INFO CAN_INVERSION_AUTO
INFO CAN_QAM_16
INFO CAN_QAM_64
INFO CAN_QAM_AUTO
INFO CAN_QPSK
INFO CAN_RECOVER
INFO CAN_TRANSMISSION_MODE_AUTO
INFO DVB API Version 5.10, Current v5 delivery system: UNDEFINED
INFO Supported delivery system:
INFO DVBT
INFO Got parameters for DVBT:
INFO FREQUENCY = 0
INFO MODULATION = QPSK
INFO BANDWIDTH_HZ = 0
INFO INVERSION = OFF
INFO CODE_RATE_HP = NONE
INFO CODE_RATE_LP = NONE
INFO GUARD_INTERVAL = 1/32
INFO TRANSMISSION_MODE = 2K
INFO HIERARCHY = NONE
INFO DELIVERY_SYSTEM = DVBT
INFO FREQUENCY = 0
INFO MODULATION = QPSK
INFO BANDWIDTH_HZ = 0
INFO INVERSION = OFF
INFO CODE_RATE_HP = NONE
INFO CODE_RATE_LP = NONE
INFO GUARD_INTERVAL = 1/32
INFO TRANSMISSION_MODE = 2K
INFO HIERARCHY = NONE
INFO DELIVERY_SYSTEM = DVBT
reply other threads:[~2015-01-02 19:36 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=54A6ED3B.9020004@keynet-technology.com \
--to=lists@keynet-technology.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 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.