linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Support for Asus MyCinema U3100Mini Plus
Date: Mon, 17 Sep 2012 02:36:00 +0300	[thread overview]
Message-ID: <50566260.1090108@iki.fi> (raw)
In-Reply-To: <50564E58.20004@schinagl.nl>

On 09/17/2012 01:10 AM, Oliver Schinagl wrote:
> On 09/16/12 19:25, Antti Palosaari wrote:
>> On 09/16/2012 06:03 PM, Oliver Schinagl wrote:
>>> I don't have windows, so capturing using windows is near impossible.
>>> Also since the vendor driver used to work, I guess I will have to dig
>>> into that more.
>>
>> You could capture data from Linux too (eg. Wireshark).
> Ah of course. I'll dig up the old vendor driver and see if I can get it
> running on 3.2 or better yet, on 3.5/your-3.6. I know there's patches
> for 3.2 but I've never tested those. Otherwise the older 2.6.2* series
> should still work.
>
>>
>> But with a little experience you could see those GPIOs reading existing
>> Linux driver and then do some tests to see what happens. For example
>> some GPIO powers tuner off, you will see I2C error. Changing it back
>> error disappears.
> I have zero experience so I'll try to figure things out. I guess you
> currently turn on/off GPIO's etc in the current driver? Any line which
> does this so I can examine how it's done? As for the I2C errors, I
> suppose the current driver will spew those out?

Those GPIOs are set in file af9035.c, functiuons: af9035_tuner_attach() 
and af9035_fc0011_tuner_callback(). For TDA18218 tuner there is no any 
GPIOs set, which could be wrong and it just works with good luck OR it 
is wired/connected directly so that GPIOs are not used at all.

> Speaking off, in my previous message, I wrote about the driver spitting
> out the following error:
> [dvb_usb_af9035]af9035_read_config =_ "%s: [%d]tuner=%02x\012"

It is the tuner ID value got from eeprom. You should take that number 
and add it to af9033.h file:
#define AF9033_TUNER_FC2580    0xXXXX <= insert number here

> None of the values where set however. Did I miss-configure anything for
> it to cause to 'forget' substituting?

What you mean? Could you enable debugs, plug stick in and copy paste 
what debugs says?

>
>>
>>> Since all the pieces should be there, fc2580 driver, af9033/5 driver,
>>> it's just a matter of glueing things together, right? I'll dig further
>>> into it and see what I can find/do.
>>
>> Correct. Tuner init (demod settings fc2580) for is needed for af9033.
>> And GPIOs for AF9035. In very bad luck some changes for fc2580 is needed
>> too, but it is not very, very, unlikely.
>>
>> This patch is very similar you will need to do (tda18218 tuner support
>> for af9035):
>> http://patchwork.linuxtv.org/patch/10547/
> I re-did my patch using that as a template (before I used your work on
> the rtl) and got the exact result.
>
> Your rtl|fc2580 combo btw (from bare memory) didn't have the fc2580_init
> stream in af9033_priv.h. What exactly gets init-ed there? The af9033 to
> work with the fc2580?

You have to add fc2580 init table to file af9033_priv.h. It configures 
all the settings needed for AF9033 demod in order to operate with FC2580 
tuner. There is some values like "tuner ID" which is passed for AF9033 
firmware, dunno what kind of tweaks it done. Maybe calculates some 
values like signal strengths and AGC values. It could work without, but 
at least performance is reduced.

regards
Antti



-- 
http://palosaari.fi/

  reply	other threads:[~2012-09-16 23:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 20:47 [PATCH] Support for Asus MyCinema U3100Mini Plus oliver
2012-09-09 20:49 ` Oliver Schinagl
2012-09-09 21:51   ` Antti Palosaari
2012-09-09 22:26     ` Oliver Schinagl
2012-09-09 22:29       ` Antti Palosaari
2012-09-10  9:58         ` Oliver Schinagl
2012-09-10 11:46           ` Antti Palosaari
2012-09-10 14:29             ` Oliver Schinagl
2012-09-10 17:28               ` Oliver Schinagl
2012-09-16 14:07                 ` Oliver Schinagl
2012-09-16 16:43                   ` Antti Palosaari
2012-09-16 15:03                     ` Oliver Schinagl
2012-09-16 17:25                       ` Antti Palosaari
2012-09-16 22:10                         ` Oliver Schinagl
2012-09-16 23:36                           ` Antti Palosaari [this message]
2012-09-17  8:25                             ` Oliver Schinagl
2012-09-17 13:02                               ` Oliver Schinagl
2012-09-17 13:16                                 ` Antti Palosaari
2012-09-17 13:26                                   ` Oliver Schinagl
2012-09-17 13:52                                     ` Antti Palosaari
2012-09-17 15:20                                       ` Oliver Schinagl
2012-09-17 20:43                                         ` Oliver Schinagl
2012-09-17 21:07                                           ` Antti Palosaari
2012-09-17 21:57                                             ` Oliver Schinagl
2012-09-18 17:18                                               ` Oliver Schinagl
2012-09-18 22:51                                                 ` Antti Palosaari
2012-09-19 10:41                                                   ` Oliver Schinagl
2012-09-19 10:53                                                     ` Antti Palosaari
2012-09-17 20:43                                         ` Oliver Schinagl
2012-09-18 22:59                                         ` Antti Palosaari
  -- strict thread matches above, loose matches on Subject: below --
2012-09-19 18:44 oliver
2012-09-19 20:52 ` Devin Heitmueller
2012-09-19 22:47   ` Oliver Schinagl
2012-09-20 18:54   ` Oliver Schinagl
2012-09-20 19:21     ` Devin Heitmueller
2012-09-19 21:36 ` Antti Palosaari
2012-09-20 18:54   ` Oliver Schinagl
2012-09-20 18:57 oliver
2012-09-20 19:15 ` Antti Palosaari
2012-09-20 19:28   ` Oliver Schinagl
2012-09-20 19:37     ` Antti Palosaari

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=50566260.1090108@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    /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).