From: Antti Palosaari <crope@iki.fi>
To: poma <pomidorabelisima@gmail.com>, Olli Salonen <olli.salonen@iki.fi>
Cc: linux-media <linux-media@vger.kernel.org>,
Jose Alberto Reguero <jareguero@telefonica.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: dvb_usb_af9015: command failed=1 _ kernel >= 4.1.x
Date: Tue, 11 Aug 2015 01:40:57 +0300 [thread overview]
Message-ID: <55C92879.5020306@iki.fi> (raw)
In-Reply-To: <55C91BD1.9010807@gmail.com>
On 08/11/2015 12:46 AM, poma wrote:
> Furthermore, to fix this issue - AF9015 DVB-T USB2.0 stick brokenness - is the responsibility of developers.
> I am here only proven tester.
>
> I hope we understand each other, and this problem will be resolved in good faith.
Your patches are implemented wrong.
When I added mxl5007t support to that driver it was DigitalNow TinyTwin
v2 I had. The rest mxl5007t dual devices using reference design IDs went
to same due to reason driver detects used tuner. My device is still
working fine, which means your device has different wiring. As 2nd tuner
attach fails it means there is communication loss to tuner. Which means
tuner is most likely hold in a reset attach time or there is some I2C
gating which prevents communication.
Patches you sent will introduce another issue. For dual tuner
configuration there could be antenna wired from tuner chip to another.
After that patch you will lose antenna signal from 2nd tuner on cases
where tuner antenna wire is loop through master tuner to slave.
So fix it correctly. Find out reason there is communication loss to 2nd
tuner on attach time. I cannot do much as I simply don't have such
hardware. And I really do not care to take any responsibility when that
kind of issues happens - it is not my job to bough every single device
from the market in able to test and fix every hardware combination.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2015-08-10 22:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 20:17 dvb_usb_af9015: command failed=1 _ kernel >= 4.1.x Jose Alberto Reguero
2015-07-07 8:48 ` poma
2015-07-13 9:48 ` poma
2015-07-31 15:03 ` poma
[not found] ` <CAAZRmGym49dG6Jj-ZeKZmy0rgr4ozph7-ggjLoWtGOvT1m4oBA@mail.gmail.com>
2015-08-10 21:46 ` poma
2015-08-10 22:40 ` Antti Palosaari [this message]
2015-08-12 23:52 ` poma
-- strict thread matches above, loose matches on Subject: below --
2015-05-08 10:20 dvb_usb_af9015: command failed=1 - stable: 4.0.2 poma
2015-05-08 10:59 ` poma
2015-05-10 10:38 ` dvb_usb_af9015: command failed=1 >= 3.19.x poma
2015-05-10 22:25 ` dvb_usb_af9015: command failed=1 _ lsdvb " poma
2015-05-11 18:43 ` dvb_usb_af9015: command failed=1 _ kernel >= 4.1.x poma
2015-05-12 14:11 ` Antti Palosaari
2015-05-13 3:56 ` poma
2015-05-16 23:07 ` Antti Palosaari
2015-05-18 19:15 ` poma
2015-05-21 21:23 ` poma
2015-05-26 12:24 ` poma
2015-07-02 23:02 ` poma
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=55C92879.5020306@iki.fi \
--to=crope@iki.fi \
--cc=jareguero@telefonica.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=olli.salonen@iki.fi \
--cc=pomidorabelisima@gmail.com \
/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).