From: Diorser <diorser@gmx.fr>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: "Antti Palosaari" <crope@iki.fi>
Subject: Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal
Date: Thu, 03 Jan 2013 22:24:27 +0100 [thread overview]
Message-ID: <op.wqctq1ej4bfdfw@quantal> (raw)
In-Reply-To: <50E37C95.3020208@iki.fi>
> I don't know why you resists to remove antenna or unplug stick, but
> even you remove antenna I am quite sure you will see similar results.
I've been simply confused by the signal reported at ffff level most of the
time, and the scanning working.
I thought the problem was a step behind with the demux error reported by
dvbsnoop wrongly used.
Can you confirm, either you personally, or someone else you know, that
AVerTV_Volar_HD_PRO_A835 using same components as A918R fully works
including tuning+scanning ?
If so, it's hard to believe that Avermedia made something different when
changing from a USB stick to Express card detected as USB, but who
knows....
> Maybe there is some GPIO controlling antenna input or switching some
> other.
I've noticed that af9035.c does not contain any GPIO settings for TDA18218
(all other tuners have).
Would it be possible to implement gpio setting for TDA18218 so that they
are used for implementations requesting it ? (just an assumption of
course). Don't know at all if this kind of information is easily available.
If necessary, although not familiar at all with debugging, I can try co
compile a specific kernel with CONFIG_DEBUG_KERNEL=y option to see if I
can grab something interesting.
Finally, it seems that fresh implementation of TDA18218 needs a bit more
investigation checked on more devices.
BTW, is the A918R patch proposal accepted to be taken into consideration,
or do I have to make a more formal GIT request ?
Regards.
Diorser.
next prev parent reply other threads:[~2013-01-03 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 21:40 AverTV_A918R (af9035-af9033-tda18218) / patch proposal Diorser
2013-01-01 22:26 ` Antti Palosaari
[not found] ` <op.wp88epxu4bfdfw@quantal>
2013-01-01 23:09 ` Diorser
2013-01-01 23:32 ` Antti Palosaari
2013-01-02 0:12 ` Diorser
2013-01-02 0:17 ` Antti Palosaari
2013-01-03 21:24 ` Diorser [this message]
2013-01-03 21:45 ` Antti Palosaari
2013-01-02 0:23 ` Diorser
2013-04-09 14:46 ` Diorser
2013-04-09 18:33 ` Antti Palosaari
2013-04-09 18:58 ` Diorser
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=op.wqctq1ej4bfdfw@quantal \
--to=diorser@gmx.fr \
--cc=crope@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).