![]() ![]() IR baud rate is slower than a non-IR device (wired/wireless keyboards for example), and evdev can respond too quickly resulting in things misbehaving. It would be worth noting that evdev is not out-of-the-box configured for the best IR experience. The MCE Remote and MCE Keyboard are already known devices to the kernel so no learning configuration is needed. This is part of the core kernel packages so no installation work is needed here. ![]() This guide does briefly touch on migration between lirc and evdev. LIRC essentially had to monitor and function with 2 receivers and not the typical one. LIRC made this difficult due to how the NUC IR receiver was designed where some inputs would show on /dev/events/input3, and others to /dev/events/input4 depending on the exact command the remote sent. Making use of MCE keyboard commands (ALT+., WIN+., CTRL+.) where the standard MCE Remote lacked. The aim for my installation was to be able to interact with an FE in as few clicks as possible on the remote. Using both of these MCE inputs means the most amount of available options. The following information has been written based on Logitech myHarmony 'Microsoft MCE Keyboard' and 'Microsoft Windows Media Center SE' devices, with the Intel DN2820FYKH NUC built-in IR receiver. IR support has been added in to the linux kernel using evdev (/dev/event/inputX) and works natively in mythbuntu14.04 and mythtv with little configuration. Lirc is typically no longer required for a range of common IR devices. ![]()
0 Comments
Leave a Reply. |