Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 06 12月, 2009 4 次提交
  3. 19 9月, 2009 4 次提交
  5. 13 9月, 2009 1 次提交
  7. 12 9月, 2009 3 次提交
    • M
      V4L/DVB (12698): em28xx: ir-kbd-i2c init data needs a persistent object · d2ebd0f8
      由 Mauro Carvalho Chehab 提交于 
      ir-kbd-i2c's ir_probe() function can be called much later (i.e. at
ir-kbd-i2c module load), than the lifetime of a struct IR_i2c_init_data
allocated off of the stack in cx18_i2c_new_ir() at registration time.
Make sure we pass a pointer to a persistent IR_i2c_init_data object at
i2c registration time.

Thanks to Brian Rogers, Dustin Mitchell, Andy Walls and Jean Delvare to
rise this question.

Before this patch, if ir-kbd-i2c were probed after em28xx, trash data
were used. After the patch, no matter what order, it is properly
reported as tested by me:

input: i2c IR (i2c IR (EM2840 Hauppaug as /class/input/input10
ir-kbd-i2c: i2c IR (i2c IR (EM2840 Hauppaug detected at i2c-4/4-0030/ir0 [em28xx #0]
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      d2ebd0f8
    • M
      V4L/DVB (12595): common/ir: use a struct for keycode tables · 715a2233
      由 Mauro Carvalho Chehab 提交于 
      Currently, V4L uses a scancode table whose index is the scancode and
the value is the keycode. While this works, it has some drawbacks:

1) It requires that the scancode to be at the range 00-7f;

2) keycodes should be masked on 7 bits in order for it to work;

3) due to the 7 bits approach, sometimes it is not possible to replace
the default keyboard to another one with a different encoding rule;

4) it is different than what is done with dvb-usb approach;

5) it requires a typedef for it to work. This is not a recommended
Linux CodingStyle.

This patch is part of a larger series of IR changes. It basically
replaces the IR_KEYTAB_TYPE tables by a structured table:
struct ir_scancode {
       u16     scancode;
       u32     keycode;
};

This is very close to what dvb does. So, a further integration with DVB
code will be easy.

While we've changed the tables, for now, the IR keycode handling is still
based on the old approach.

The only notable effect is the redution of about 35% of the ir-common
module size:

   text    data     bss     dec     hex filename
   6721   29208       4   35933    8c5d old/ir-common.ko
   5756   18040       4   23800    5cf8 new/ir-common.ko

In thesis, we could be using above u8 for scancode, reducing even more the size
of the module, but defining it as u16 is more convenient, since, on dvb, each
scancode has up to 16 bits, and we currently have a few troubles with rc5, as their
scancodes are defined with more than 8 bits.

This patch itself shouldn't be doing any functional changes.
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      715a2233
    • M
      V4L/DVB (12591): em28xx: Add entry for GADMEI UTV330+ and related IR keymap · 6d888a66
      由 Mauro Carvalho Chehab 提交于 
      [mchehab@redhat.com: Fix a few wrong IR keymaps]
Signed-off-by: NShine Liu <shinel@foxmail.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      6d888a66
  9. 31 8月, 2009 1 次提交
  11. 14 8月, 2009 1 次提交
  13. 25 7月, 2009 6 次提交
  15. 06 7月, 2009 1 次提交
  17. 23 6月, 2009 1 次提交
  19. 17 6月, 2009 8 次提交
  21. 07 4月, 2009 1 次提交
  23. 30 3月, 2009 9 次提交