hal 0.5.10: unable to configure a remote control
Jimmy Jazz
Jimmy.Jazz at gmx.net
Thu Feb 28 10:09:18 PST 2008
Hello,
I'm trying to configure a freecom (avermedia dvb) IR remote control
without success. Also i cannot figure out where the problem is.
I'm using hal 0.5.10 and a kernel 2.6.24
The remote control is indeed recognized. For every key pressed, the
kernel returns something like,
kernel: key: f0 67 85 3f 0
kernel: key: f0 67 85 5f 0
...
I have defined the following policy
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<!-- IR Remote Receiver, Freecom -->
<match key="info.bus" string="usb_device">
<match key="usb_device.vendor_id" int="0x14aa">
<match key="usb_device.product_id" int="0x0226">
<append key="info.capabilities" type="strlist">input</append>
<append key="input.keymap.data" type="strlist">74:mute</append>
<append key="input.keymap.data" type="strlist">96:power</append>
<append key="input.keymap.data"
type="strlist">95:volumedown</append>
<append key="input.keymap.data"
type="strlist">76:volumeup</append>
<append key="input.keymap.data"
type="strlist">82:channeldown</append>
<append key="input.keymap.data"
type="strlist">86:channelup</append>
<append key="input.keymap.data" type="strlist">28:last</append>
<append key="input.keymap.data" type="strlist">36:zoom</append>
<append key="input.keymap.data" type="strlist">10:1</append>
<append key="input.keymap.data" type="strlist">11:2</append>
<append key="input.keymap.data" type="strlist">12:3</append>
<append key="input.keymap.data" type="strlist">13:4</append>
<append key="input.keymap.data" type="strlist">14:5</append>
<append key="input.keymap.data" type="strlist">15:6</append>
<append key="input.keymap.data" type="strlist">16:7</append>
<append key="input.keymap.data" type="strlist">17:8</append>
<append key="input.keymap.data" type="strlist">18:9</append>
<append key="input.keymap.data" type="strlist">19:0</append>
<append key="info.capabilities"
type="strlist">input.keymap</append>
<append key="info.locked" type="bool">true</append>
<append key="info.locked.reason" type="string">The remote
control is currently in use</append>
</match>
</device>
</deviceinfo>
evdev still interprets the device as a standard KEYBOARD. It doesn't
understand the redefined keycodes. The native keymap of the remote
control makes the device unusable with the gnome/compiz environment, but
xev gives a response to every key I pressed.
Lircd didn't help either and will also conflict with evdev. It is unable
to get an exclusive access to the remote control. Irw hardly ever react.
I finally add the following fdi in /etc/hal/fdi/preprobe
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<!-- IR Remote Receiver, Freecom -->
<match key="info.bus" string="usb_device">
<match key="usb_device.vendor_id" int="0x14aa">
<match key="usb_device.product_id" int="0x0226">
<merge key="info.ignore" type="bool">true</merge>
</match>
</match>
</match>
</device>
</deviceinfo>
to force hal to ignore the remote as well as xorg. Things goes a bit
better using lircd... most of the keys I pressed have given a immediate
response from irw but still without an exclusive access.
Is there a better way to remap keys with hal?
Has someone managed to configure an ir remote control with the last
stable kernel, hal or lircd and X?
How can i have a exclusive access to the device in xorg ?
Your help is very much appreciated.
Regards
Jj
More information about the hal
mailing list