The unused keys and unmatched entries are written as comments into the generated file. An 'illegal' key i.
However, it's perfectly possible to use it later on while manually modifying the lircrc files. A minimal such might look like. The -s option simply reports all key symbols not in namespace. If present, duplicated keys are also reported. The script uses a simple, line-oriented format to represent the lircrc files. I have the specs for the Hauppauge remote control. I managed to send IR signals to my satellite receiver using my linux box within 1 hour!
Receiving of IR signals was also possible but has some limitations. You can see this as a motivation for you to work on support for IrDA compliant hardware as I don't have the time to do it myself. Linux Links Linux Documentation Project www. What is LIRC? Supported remote controls There are some config files for remote controls at the remotes database.
This is about devices and counting. These devices should work with the general drivers or if it lacks timing info the driver used to create them. Supported capture devices Besides a remote control you also need a capture device to read the data from the remote.
News [May ] lirc In memoriam Manuel Estrada Sainz. The last duration should represent a pulse. Each line in this section contains a parameter followed by the value or values that should be assigned to that parameter. Parameters are optional unless otherwise stated.
All values are decimal integers that are either dimensionless or have units of microseconds unless otherwise stated. Hexadecimal numbers should be prefixed by 0x. If the remote does not have a particular "feature," then the line may be omitted. The button code is sent just after the pre signal and just before the post signal. Recent Linux kernels have built-in support for IR remotes.
Using that, pressing an up-arrow on the remote works the same way as pressing the up-arrow on a keyboard. This is a modern "just works" solution. On the other hand, LIRC is an old style linux application which can be tweaked to do almost anything, but is tricky to setup.
So, why would you use LIRC? So, while the kernel built-in handling works out of the box in many cases, there are still scenarios when LIRC is the right tool. From 0. This should work out of the box with the following limitations:. The easy way to check is to try the remotes without lircd running. If it works this way, it should also work using lircd.
This should list a single entry rc0. If you want to use the default configuration you should start and enable the lircd service and possibly define lircrc files for your applications. See systemd-setup. Generally speaking everything that can receive or send infrared signals can be supported by LIRC.
The project began with support for home-brew receivers and transmitters for the serial port and later support for similar hardware for the parallel port was added. At that time the focus of the project was to provide an infrared solution that was both very cheap and easy to assemble.
There is some more info on this in Appendix Current versions of LIRC now support many more commercially available solutions. As a starter, it can use all devices supported by the kernel. Drivers for even more hardware are likely to appear in the future. If you are a programmer who wants to maintain such a driver you are welcome to join the project. LIRC can be run together with the kernel in different ways. You need to decide on a general approach. Using the LIRC data requires application support.
Support for LIRC is common in typical linux htpc applications like mythtv, kodi and vlc; of course also LIRC applications like irexec, lircmd and irpty supports this. Unless there is reason to use lirc above this is probably the way to go. If you need to use lirc, there are two cases depending on if your remote is supported by the kernel or not. See lircd-uinput 8.
The lirc configuration consists of several files described in Appendix There are some tools to aid in the configuration listed in programs overview.
This is described in Appendix 8. To use multiple capture devices you need to setup multiple lircd instances as described in Appendix 9. Some aspects on running as a non-root user is described in Appendix To determine the driver to use you might need to know the name of your capture device, what module the kernel has loaded for it and the kernel device it's connected to. If our remote is bundled with a capture device such as a usb dongle, your first stop is the remote database.
If you can find your device here, look in lircd. Here you can learn that this file was recorded using the awlibusb driver. Take a note to the final decision. Furthermore, since ir-keytable finds the device you know that the driver is part of the rc subsystem. Not all devices are recognized by ir-keytable, though. Next step is to inspect dmesg, possibly after reconnecting your device.
If you have a standard IR remote which is recognized by the kernel you can find how it's registered as rc If you just find something like this you have a device which isn't an IR device in this case an RF remote :. Even if you have an IR device, you might see something like this if the kernel sees it as a keyboard rather than a remote.
For devices like these which not are registered as rc devices and thus not recognized by ir-keytable you might need to find out the corresponding event device as described in Appendix 2. After selecting the driver and device you should check if there is any driver documentation. After this, check the driver and device using using e.
The lirc-setup tool can be used to run mode2 with different drivers and devices in a GUI environment. If you are to use the devinput driver, read on. Otherwise proceed to Getting the key symbols using lirc driver. If you're lucky, your remote is already supported by the kernel. This is described in appendix 2. Press buttons on the remote. If it starts to print out scan codes and key symbols everything is fine. Otherwise, try to change the protocol see the ir-keytable manpage. If this doesn't work, it might be the end of the road and you might need to use the lirc driver option instead.
Check that all buttons generate output when testing. If there are buttons which are not mapped no key symbol you might not be able to fix this unless you go for the lirc driver option to change the key symbol is perfectly possible, but probably not what you want here. If the devinput. This might become necessary if the running kernel is different from the one used when packaging the lirc files.
Press remote buttons.
0コメント