From: Matthias Schwarzott <zzam@gentoo.org>
To: "Sven Müller" <xpert-reactos@gmx.de>, linux-media@vger.kernel.org
Subject: Re: Aw: Re: Re: Card with si2165
Date: Wed, 18 Dec 2013 07:05:31 +0100 [thread overview]
Message-ID: <52B13B2B.4040401@gentoo.org> (raw)
In-Reply-To: <trinity-694fffe1-2ff0-46db-9cd8-ec08b156703e-1387230575663@3capp-gmx-bs08>
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
prev parent reply other threads:[~2013-12-18 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 0:12 Card with si2165 "Sven Müller"
2013-12-15 20:25 ` Matthias Schwarzott
2013-12-16 8:26 ` Aw: " "Sven Müller"
2013-12-16 20:20 ` Matthias Schwarzott
[not found] ` <trinity-694fffe1-2ff0-46db-9cd8-ec08b156703e-1387230575663@3capp-gmx-bs08>
2013-12-18 6:05 ` Matthias Schwarzott [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=52B13B2B.4040401@gentoo.org \
--to=zzam@gentoo.org \
--cc=linux-media@vger.kernel.org \
--cc=xpert-reactos@gmx.de \
/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