<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Martin: I've been seeing this come up for the last release or two.  I've been stuffing them into LIRC when they come up.  I'm not sure if it's the right place to put them, but it works for now until the evdev driver gets full support for all the other buttons. Regards Martin Pitt wrote: <blockquote cite="mid:20090212195240.GB23671@piware.de" type="cite"> <pre wrap="">Hello all, We got a rather curious bug report in Ubuntu: <a class="moz-txt-link-freetext" href="https://launchpad.net/bug/322483">https://launchpad.net/bug/322483</a> The problem is that some common infrared devices are detected as input devices in the modern -evdev world, and thus end up being handled as such: udi = '/org/freedesktop/Hal/devices/temp/77' info.parent = '/org/freedesktop/Hal/devices/pci_14f1_8800' (string) info.subsystem = 'input' (string) input.device = '/dev/input/event6' (string) input.originating_device = '/org/freedesktop/Hal/devices/pci_14f1_8800' (string) input.product = 'cx88 IR (Leadtek Winfast 2000XP' (string) linux.device_file = '/dev/input/event6' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'input' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1e.0/0000:06:01.0/input/input6/event6' (string) However, with -evdev you can only use the digit and Enter keys. Thus the bug reporter proposed to set rules like <match key="info.product" contains_ncase="saa7134 ir"> <merge key="info.ignore" type="bool">true</merge> </match> <match key="info.product" contains_ncase="IR-Receiver"> <merge key="info.ignore" type="bool">true</merge> </match> <match key="info.product" contains_ncase="cx88 IR"> <merge key="info.ignore" type="bool">true</merge> </match> <match key="info.product" contains_ncase="bttv IR"> <merge key="info.ignore" type="bool">true</merge> </match> to ignore these devices as input devices. This will allow LIRC to use them properly. Now, I haven't encountered this kind of quirk so far, and I'm not sure what its home should be. - hal-info -> has lots of hw specific quirks, also for input devices, but doesn't have this kind of quirk so far - hal itself -> already ships rules to set input.x11_driver="evdev" for devices with input.keys capabilities, so it would be kind of "you broke it, you fix it" - lirc packages -> would be correct in the sense that if you don't have lirc installed, you can still use the devices in a restricted manner Right now I'm leaning towards stuffing them into lirc. Any opinions on this? Thanks, Martin </pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ hal mailing list <a class="moz-txt-link-abbreviated" href="mailto:hal@lists.freedesktop.org">hal@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/hal">http://lists.freedesktop.org/mailman/listinfo/hal</a> </pre> </blockquote> <div class="moz-signature">-- <title></title> Mario Limonciello Dell | Linux Engineering <a class="moz-txt-link-abbreviated" href="mailto:mario_limonciello@dell.com">mario_limonciello@dell.com</a> </div> </body> </html>