The nf is located in /var/lib/vdr/nf and belongs to the templated files. The customization of this mapping is decribed later in this chapter. Otherwise, eventlircd cannot process the buttons properly. This requires, that the names of all buttons in the lirc configuration files, the key tables from ir-core and from devices that are directly attached to eventlird have to comply with the naming convention in the input.h header file of the kernel and fit to the nf file. This ensures that the remote control works properly in both VDR and XBMC. YaVDR is optimized for a standardized nf file for VDR and a matching Lircmap.xml for XBMC. If there are any lirc receivers that do not work out of the box, the appropriate udev rules have to be created manually.Ĭaution when changing the remote contol in the nf! For these devices, no further configuration via the web interface is required. In theory, it is even possible to start multiple lircd instances for different input devices with different configuration at the same time.įor USB lirc receivers, an udev rule in /lib/udev/rules.d/les and the lircd_helper, an instance of the lirc daemon is started, and the drivers and nf files that specified in the udev rule are used. Thus, lircd can be used together with other input devices. You can instruct Lircd via the switch -uinput to direct its key presses to an device underneath /dev/input/. The configurations fo all these devices can be stored on your system at the same time because udev activates the configuration only for attached devices.Ī translation table can (depending on device and/or driver) be passed to eventlircd to customized the key layout (so called evmaps). USB devices), the proper configuration can be attached via udev rules. Since some devices can definetely recognized (e.g. This is done by udev rules.įor some devices, this is already working in the standard configuration (devices managed by rc-core, devices that are used by yaVDR developers, or also community contributed configurations that were given to the yaVDR team).įrom the application point of view, the output of eventlircd looks as if it would come from one single input device. This is a one of the greatest advantages of this solution: eventlircd provides a lirc socket for the VDR when it starts, while the input devices are attached afterwards as soon they are recognized.Įventlircd recognizes the devices in its field of responsibility by attributes that can assigned to the devices during its initalization. In these cases, eventlircd will forward them without further processing (unless the are remapped to a key event).Įventlircd recognizes input devices via an udev-attribute, even when a daemon attaches them after the start of the system. Inputs from pointer devices (such as mice, touchpads, tablets) are also attached to the input interface. Although this interface is not a regular keyboard driver, it registers those devices as kernel input devices. Jarod Wilson ported already most of the existing Lirc drivers as well as some drivers for remote controls connected to DVB adapters to this new interface. Finally, there is an new interface for remote controls which is called rc-core. Other remote controls that are attached to DVB adapters register themselves partially as keyboards, too. regular keyboards or also remote controls, which are registered as a keyboard by their driver. Basically, this is similar to the function of the remote plugin, with the exception that only these keys are assessed, where a keymap is available. Eventlircd translated key presses of kernel input devices into Lirc key presses.
0 Comments
Leave a Reply. |