From: Antti Palosaari <crope@iki.fi>
To: Nick Burch <v4l@gagravarr.org>
Cc: linux-media@vger.kernel.org
Subject: Re: KWorld USB DVB-T TV Stick II 395U almost but not quite working
Date: Sat, 11 Jul 2009 00:08:03 +0300 [thread overview]
Message-ID: <4A57ADB3.9090805@iki.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0907101934320.22332@urchin.earth.li>
On 07/10/2009 09:52 PM, Nick Burch wrote:
> usb 2-4: new high speed USB device using ehci_hcd and address 4
> usb 2-4: configuration #1 chosen from 1 choice
> dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in cold
> state, will try to load a firmware
> usb 2-4: firmware: requesting dvb-usb-af9015.fw
> dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
> dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in warm
> state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new adapter (KWorld USB DVB-T TV Stick II (VS-DVB-T 395U))
> af9013: firmware version:4.95.0
> DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
No tuner.
> After this, /dev/dvb/adapter0/ exists, and contains the entries
> demux0 dvr0 frontend0 net0
> Checking dmesg after a failed scan run, I see these two entries:
> af9015: command failed:2
> qt1010 I2C read failed
>
>
> Am I right in thinking from this that it's the qt1010 tuner that's the
> problem? If so, can anyone suggest what I should do next to debug the
> issue further?
Tuner does not attach - I2C messages towards tuner are failing. That's
most probably due to wrong GPIOs, tuner is usually powered by GPIO pin.
It can also be wrong I2C address of tuner. You should take sniffs and
look correct GPIO and I2C from there.
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2009-07-10 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 18:52 KWorld USB DVB-T TV Stick II 395U almost but not quite working Nick Burch
2009-07-10 21:08 ` Antti Palosaari [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=4A57ADB3.9090805@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=v4l@gagravarr.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