From: Vincent McIntyre <vincent.mcintyre@gmail.com>
To: linux-media@vger.kernel.org
Cc: kernel@techmunk.com
Subject: rtl28xx Leadtek
Date: Sat, 16 May 2015 13:23:06 +1000 [thread overview]
Message-ID: <20150516032301.GA41435@shambles.windy> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Hi,
I have been trying to get support going for a
Leadtek WinFast DTV2000DS Plus (usbid 0413:6f12)
Christian Dale (cc:d) posted a patch a while ago
and since that time there have been a few patches
from Olle and others that have significantly improved things.
However I am still having issues with the card;
sometimes it does not scan any of the multiplexes
I look at with it, sometimes it does some of them
and sometimes it pulls out some program ids on one
mulitplex but not the others in the scan.
The behaviour is different between the two tuners
on the card as well.
I've written a test script that turns on various
kernel dynamic debug entries and tries to scan,
using the old dvb-apps 'scan' (1.1.1+rev1500)
and the latest dvbv5-scan from git.
Would anyone on the list interested in helping
please take a look at the attached logs of the
run I did? It includes the script output and
what was happening in syslog at each step.
There should be no signal issues, as the same
test script on the same system with the same
coax input works perfectly when I swap the Leadtek
for a DVICO card using the cx23885 driver.
Both drivers are built from the media_build git.
My questions:
- are there debug items that could be turned on or off
to help diagnose the issues?
- are there some perf traces that could be run that
would be helpful?
Kind regards
Vince
[-- Attachment #2: rtltest.tar.bz2 --]
[-- Type: application/octet-stream, Size: 150083 bytes --]
next reply other threads:[~2015-05-16 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 3:23 Vincent McIntyre [this message]
2015-05-16 6:37 ` rtl28xx Leadtek Eyal Lebedinsky
2015-05-17 11:55 ` Vincent McIntyre
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=20150516032301.GA41435@shambles.windy \
--to=vincent.mcintyre@gmail.com \
--cc=kernel@techmunk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox