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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
