From: Andy Walls <awalls@md.metrocast.net>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Janne Grunau <j@jannau.net>, Jarod Wilson <jarod@redhat.com>
Subject: Re: [PATCH] hdpvr: enable IR part
Date: Sat, 15 Jan 2011 09:41:21 -0500 [thread overview]
Message-ID: <1295102481.3258.11.camel@localhost> (raw)
In-Reply-To: <0EADA025-77B0-4E8B-A649-F3BE6F2E437B@wilsonet.com>
On Sat, 2011-01-15 at 00:37 -0500, Jarod Wilson wrote:
> On Jan 14, 2011, at 11:35 PM, Andy Walls wrote:
>
>
> A single button press w/ir-kbd-i2c debugging and your patch:
>
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
> ir-kbd-i2c: ir_poll_key
> ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 54 00 ....T.
> ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=21
>
FWIW, here's what an HVR-1600 and ir-kbd-i2c dumped out for me:
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 24 00 ....$.
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=9
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 24 00 ....$.
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=9
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
[...]
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 de 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t0 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 80 00 00 fe 08 00 ......
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=30 code=2
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
ir-kbd-i2c: get_key_haup_common: received bytes: 00 00 00 00 00 00 ......
I did a momentary press of button '9' and got a single '9'.
I did a press and hold of button '2' during which I accidentally pointed
the remote away from the sensor and then back. IIRC I got one '2' and
then many '2''s after an initial lag. (What I might expect from holding
down a keybard key.)
I did a following momentary press of button '2'. I can't recall if I got
one or many '2''s for that.
Regards,
Andy
next prev parent reply other threads:[~2011-01-15 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 19:54 [PATCH] hdpvr: enable IR part Jarod Wilson
2011-01-14 21:44 ` Andy Walls
2011-01-14 22:08 ` Jarod Wilson
2011-01-15 2:30 ` Jarod Wilson
2011-01-15 4:35 ` Andy Walls
2011-01-15 5:37 ` Jarod Wilson
2011-01-15 5:53 ` Jarod Wilson
2011-01-15 6:56 ` Jarod Wilson
2011-01-15 21:56 ` Andy Walls
2011-01-15 22:10 ` Jarod Wilson
2011-01-15 14:41 ` Andy Walls [this message]
2011-01-15 21:46 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2011-01-15 12:50 Andy Walls
2011-01-15 15:26 ` Andy Walls
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=1295102481.3258.11.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=j@jannau.net \
--cc=jarod@redhat.com \
--cc=jarod@wilsonet.com \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
/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