From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>, linux-media@vger.kernel.org
Cc: kapetr@mizera.cz
Subject: Re: [PATCH] af9035: Move it913x single devices to af9035
Date: Sun, 09 Feb 2014 12:46:41 +0200 [thread overview]
Message-ID: <52F75C91.5080507@iki.fi> (raw)
In-Reply-To: <1391936396.2893.18.camel@canaries32-MCP7A>
Moi Malcolm!
On 09.02.2014 10:59, Malcolm Priestley wrote:
> On Sat, 2014-02-08 at 16:11 +0000, Malcolm Priestley wrote:
>> The generic v1 and v2 devices have been all tested.
>>
>> IDs tested
>> USB_PID_ITETECH_IT9135 v1 & v2
>> USB_PID_ITETECH_IT9135_9005 v1
>> USB_PID_ITETECH_IT9135_9006 v2
>>
>> Current Issues
>> There is no signal on
>> USB_PID_ITETECH_IT9135 v2
>>
>> No SNR reported all devices.
>>
>> All single devices tune and scan fine.
>>
>> All remotes tested okay.
>>
>> Dual device failed to register second adapter
>> USB_PID_KWORLD_UB499_2T_T09
>> It is not clear what the problem is at the moment.
> Hi Antti
>
> I have found the problem here.
>
> state->eeprom_addr + EEPROM_2ND_DEMOD_ADDR
>
> contains no value
>
> So on 9135 devices register 0x4bfb and the I2C address
> (state->af9033_config[1].i2c_addr) need to be set to 0x3a.
>
> I have only manually changed these and both adapters work fine.
>
> Also, I can't find pick up for register 0xcfff although it appears
> to be on by default.
>
> I will try and do a patch later and the patch for remaining ids in
> it913x.
Good!
That non-working dual device must be IT9135 v2 as I have one dual
TerraTec, which is working and is build upon version 1 of IT9135. I have
no v2 dual device.
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2014-02-09 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:11 [PATCH] af9035: Move it913x single devices to af9035 Malcolm Priestley
2014-02-09 8:59 ` Malcolm Priestley
2014-02-09 10:46 ` 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=52F75C91.5080507@iki.fi \
--to=crope@iki.fi \
--cc=kapetr@mizera.cz \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@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