From: Vanessa Ezekowitz <vanessaezekowitz@gmail.com>
To: stuart <stuart@xnet.com>, video4linux-list@redhat.com
Subject: Re: KWorld 120 IR control?
Date: Thu, 16 Oct 2008 15:10:48 -0500 [thread overview]
Message-ID: <200810161510.48208.vanessaezekowitz@gmail.com> (raw)
In-Reply-To: <48F753FC.4030901@xnet.com>
On Thursday 16 October 2008 9:47:24 am stuart wrote:
>
> [off list - as this doesn't add much additional info]
>
> >> I looked and found an 8 and 16 pin SMD IC on my kworld 120. The 16 pin
> >> device turned out to be a multi-bit A/D converter, not an I2C
> >> controller. After reading the above again I believe I understand what
> >> 20 pin device you are talking about. Just right of the composite video
> >> input past the Xtl in this photo:
> >> http://c1.neweggimages.com/NeweggImage/productimage/15-260-007-15.jpg
> >> ...I'll have to take another look.
>
> Interesting, I can not read any writing on that chip. All I see is a
> green dot probably identifying pin 1. If this is a common i2c
> controller - why bother? Or are the KS003 and KS007 custom chips?
>
> > Does any unknown device show up with cx88xx i2c_scan=1?
If by this you mean to add an appropriate line to /etc/modprobe.d/options... Here's what I got in dmesg when I did this (after a clean reboot with no cx88-related modules loaded):
cx88[0]: i2c scan: found device @ 0x32 [???]
cx88[0]: i2c scan: found device @ 0x34 [???]
cx88[0]: i2c scan: found device @ 0x66 [???]
cx88[0]: i2c scan: found device @ 0xa0 [eeprom]
cx88[0]: i2c scan: found device @ 0xc2 [tuner (analog/dvb)]
If you need more from the dmesg output, let me know.
--
"Life is full of positive and negative events. Spend
your time considering the former, not the latter."
Vanessa Ezekowitz <vanessaezekowitz@gmail.com>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-16 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 20:07 KWorld 120 IR control? stuart
2008-09-14 22:33 ` hermann pitton
2008-09-15 20:40 ` stuart
2008-09-15 22:04 ` hermann pitton
2008-10-14 14:32 ` stuart
2008-10-14 19:10 ` hermann pitton
2008-10-14 19:38 ` stuart
2008-10-14 21:04 ` hermann pitton
2008-10-14 23:54 ` Vanessa Ezekowitz
2008-10-15 20:32 ` hermann pitton
2008-10-16 3:59 ` stuart
2008-10-16 6:57 ` hermann pitton
[not found] ` <48F753FC.4030901@xnet.com>
2008-10-16 20:10 ` Vanessa Ezekowitz [this message]
2008-10-16 22:45 ` hermann pitton
2009-01-26 23:42 ` stuart
2009-01-27 15:15 ` Vanessa Ezekowitz
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 17:38 Vanessa Ezekowitz
2008-10-25 16:31 ` stuart
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=200810161510.48208.vanessaezekowitz@gmail.com \
--to=vanessaezekowitz@gmail.com \
--cc=stuart@xnet.com \
--cc=video4linux-list@redhat.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