Card with si2165

Card with si2165

["Sven Müller"]

Hello!

I found with google, that some people were disscussing this chip. 
Has anyone written drivers? I own a card this chip, maybe I can help to test it....

Re: Card with si2165

[Matthias Schwarzott]

On 15.12.2013 01:12, "Sven Müller" wrote:
> Hello!
> 
> I found with google, that some people were disscussing this chip. 
> Has anyone written drivers? I own a card this chip, maybe I can help to test it....
> 
Hello Sven,

I am trying to write a driver for SI2165 to get my WinTV-HVR 930C-HD
running.
What device do you have?

I posted my current version here:
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/71692

See also:
http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-930C-HD
http://www.linuxtv.org/wiki/index.php/Silicon_Labs_si2165

Getting tests and or i2c dumps would be really cool.

Regards
Matthias

Aw: Re: Card with si2165

["Sven Müller"]

> Hello Sven,
> 
> I am trying to write a driver for SI2165 to get my WinTV-HVR 930C-HD
> running.
> What device do you have?
> 
> I posted my current version here:
> http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/71692
> 
> See also:
> http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-930C-HD
> http://www.linuxtv.org/wiki/index.php/Silicon_Labs_si2165
> 
> Getting tests and or i2c dumps would be really cool.
> 
> Regards
> Matthias

I have a Hauppauge WINTV HVR 5500-HD.

Sven

Re: Aw: Re: Card with si2165

[Matthias Schwarzott]

On 16.12.2013 09:26, "Sven Müller" wrote:
> 
> I have a Hauppauge WINTV HVR 5500-HD.
> 

Hi

I think first you should check if this is exactly the same card as you
have: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-5500

Then either update this page or create a new one for your card.
Please also add pictures from front/back of your card.

As far as I understand the HVR 5500-HD is not yet supported in any way.
Best you follow this page in the wiki:
http://linuxtv.org/wiki/index.php/Development:_How_to_add_support_for_a_device

Maybe it is enough to use the cx2388x driver and do an i2c scan to find
out about the addresses of the components combined with chip names.

But most likely at least some values need to be compared to windows.
I have not yet tried sniffing PCI-traffic, but there is some work to
pass pci traffic between qemu and real pci cards.

Regards
Matthias

Re: Aw: Re: Re: Card with si2165

[Matthias Schwarzott]

On 16.12.2013 22:49, "Sven Müller" wrote:
> 
> 
>> Gesendet: Montag, 16. Dezember 2013 um 21:20 Uhr
>> Von: "Matthias Schwarzott" <zzam@gentoo.org>
>> An: "Sven Müller" <xpert-reactos@gmx.de>, linux-media@vger.kernel.org
>> Betreff: Re: Aw: Re: Card with si2165
>>
>> On 16.12.2013 09:26, "Sven Müller" wrote:
>>>
>>> I have a Hauppauge WINTV HVR 5500-HD.
>>>
>>
>> Hi
>>
>> I think first you should check if this is exactly the same card as you
>> have: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-5500
>>
> 
> It's the same card.

So could you please check if the information is up to date.

* Add missing components, e.g. si2165
* What about the tuner for DVB-C/T - it could be a tda18271 - can you
verify this?
* Maybe add a picture if you can take one.
* Add dmesg of the cx23885 driver if it at least tries to do stuff with
the card.
* You can pass cx23885 the parameter i2c_scan, but I think it will not
differ from your i2cdetect calls.

> i2c-9	i2c       	cx23885[0]                      	I2C adapter
> i2c-10	i2c       	cx23885[0]                      	I2C adapter
> i2c-11	i2c       	cx23885[0]                      	I2C adapter
> 
>From cx23885 sources I guess bus 9 and 10 are the external buses:

> # i2cdetect -y 9
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- 05 -- -- -- -- -- 0b -- -- -- -- 
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 70: -- -- -- -- -- -- -- --                         
> # i2cdetect -y 10
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 
> 60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 70: -- -- -- -- -- -- -- --                         
Here could be a tuner at 0x60.

> # i2cdetect -y 11
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 
> 40: -- -- -- -- 44 -- -- -- -- -- -- -- 4c -- -- -- 
> 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 70: -- -- -- -- -- -- -- --            
> 
Compare to cx23885-i2c.c:
At 0x44 is the internal cx25837
At 0x4c is the flatiron

To detect more you need the correct GPIO configuration I think, so that
all components are out of reset state.

If dmesg also shows the tda18271, most likely this is also used for DVB-C/T.
Now you need to find out how to set the GPIOs so that you can talk to
si2165 via i2c.

And second, how this type of cards handle the multiple frontend stuff.

I wonder if the subdevice id of your card is really identical to
HVR4400, if yes, the eeprom is necessary to detect the exact used
components.

Regards
Matthias