When comparing lirc-i2c and ir-kbd-i2c/bttv-input logic, a difference
was noticed. As lirc-i2c will be removed soon, store the difference on
a comment inside ir-kbd-i2c, in order to preserve the knowledge we
have about that remote controller.

Signed-off-by: Mauro Carvalho Chehab <[email protected]>

diff --git a/drivers/media/video/bt8xx/bttv-input.c 
b/drivers/media/video/bt8xx/bttv-input.c
index 7f48306..97793b9 100644
--- a/drivers/media/video/bt8xx/bttv-input.c
+++ b/drivers/media/video/bt8xx/bttv-input.c
@@ -354,6 +354,18 @@ static int get_key_pv951(struct IR_i2c *ir, u32 *ir_key, 
u32 *ir_raw)
                return 0;
        dprintk(KERN_INFO DEVNAME ": key %02x\n", b);
 
+       /*
+        * NOTE:
+        * lirc_i2c maps the pv951 code as:
+        *      addr = 0x61D6
+        *      cmd = bit_reverse (b)
+        * So, it seems that this device uses NEC extended
+        * I decided to not fix the table, due to two reasons:
+        *      1) Without the actual device, this is only a guess;
+        *      2) As the addr is not reported via I2C, nor can be changed,
+        *         the device is bound to the vendor-provided RC.
+        */
+
        *ir_key = b;
        *ir_raw = b;
        return 1;
-- 
1.7.3.4


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to