From: stuart <stuart@xnet.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com
Subject: Re: KWorld 120 IR control?
Date: Wed, 15 Oct 2008 22:59:36 -0500 [thread overview]
Message-ID: <48F6BC28.9070703@xnet.com> (raw)
In-Reply-To: <1224102756.2683.67.camel@pc10.localdom.local>
hermann pitton wrote:
> Hi Vanessa,
>
> Am Dienstag, den 14.10.2008, 18:54 -0500 schrieb Vanessa Ezekowitz:
>> On Tuesday 14 October 2008 4:04:42 pm hermann pitton wrote:
>>> thanks, I tried to look it up better this time and saw this already at
>>> the linuxtv wiki. Also found a reasonable picture, but not good enough.
>>> At least no 16 pins KS007 so far.
>
> this needs correction. KS003 and KS007 both have 18 pins and are clearly
> marked with these names. They are on many recent Kworld products.
>
>> I have sent Hermann some high resolution photos of my Kworld ATSC 120 by direct email.
>>
>> Hermann, feel free to pass these around if you need to; if you need better ones, or you want me to direct my camera to a particular spot on the card, please let me know.
>
> Thanks, but no luck on the bttv-gallery so far.
> Maybe somebody else saw it already.
>
> It should be the chip with 20 pins in position U9, unfortunately only
> marked with a green colored spot and connected to the xtal X0 16MHz in
> front of the radio RF input.
>
> We have an unknown gpio remote controller marked with a grey spot on the
> saa7131e Kworld TV Studio Terminator, but 18 pins and 20MHz clock and
> that smaller grey remote with 36 keys. Usually RM-Kum01 and xtal 4MHz.
> Also one only with a blue spot on Kworld Creator TV MCE 100 Pro and
> remote with 32 keys. (BTW, some rare KS008 is on Cinergy 250 PCI)
>
> case SAA7134_BOARD_KWORLD_TERMINATOR:
> ir_codes = ir_codes_pixelview;
> mask_keycode = 0x00001f;
> mask_keyup = 0x000060;
> polling = 50; // ms
> break;
>
> On cx88-input.c all Kworld stuff has that too.
>
> ir->gpio_addr = MO_GP1_IO;
> ir->mask_keycode = 0x1f;
> ir->mask_keyup = 0x60;
>
> But you switch already some pins within mask_keycode on MO_GP1_IO.
> Maybe on MO_GP0_IO. Is that gpio0 and gpio2 stuff needed at all in the
> card's entry? If not, but some of the first 8 gpios are connected, might
> be the remote. Needs to have the cx23880 pinning at hand, but seems
> there are no simply visible connections from that green marked chip.
> Maybe worth to try with mask_keycode = 0x0.
>
> On the other hand, on the backside seem to be two lines from that chip
> more in direction to the tuner. Could hang on i2c there, but can't tell.
> Does any unknown device show up with cx88xx i2c_scan=1?
>
> For now, known Kworld stuff has various IR controllers with 18 pins.
> It is not one of the newer KS00x i2c devices here and a controller with
> 20 pins and 16MHz clock seems to be new. How many keys/buttons has the
> remote?
>
> That is not much, but hopefully better than nothing.
> I can't exclude that the controller needs some sort of
> initialization/activation or maybe even uses a new IR protocol,
> but testing in the above directions should not be too much work.
>
> Cheers,
> Hermann
>
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.
The remote for my kworld 120 has 35 keys. (My kworld 110 remote has
about 45 keys.)
...thanks for your help.
--
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 4:01 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 [this message]
2008-10-16 6:57 ` hermann pitton
[not found] ` <48F753FC.4030901@xnet.com>
2008-10-16 20:10 ` Vanessa Ezekowitz
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=48F6BC28.9070703@xnet.com \
--to=stuart@xnet.com \
--cc=hermann-pitton@arcor.de \
--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