37dc6ef716
Using $id to get the rcX device name from the SUBSYSTEMS match,
as used by the upstrem v4l-utils udev rule, is easier and more
stable than using IMPORT{parent}, which needs to transmit info across
two levels (rcX->inputY->eventZ) and breaks with kernel 4.20.
Instead of running a shell script to check for the existance of
/storage/.config/rc_maps.cfg we can use the builtin udev TEST
function.
Also it's better to use ENV variables prefixed with a dot as
they are used only locally in the udev rule file and don't need
to be persisted in the udev database or exported to external tools.
Signed-off-by: Matthias Reichl <hias@horus.com>
LibreELEC
LibreELEC is a 'Just enough OS' Linux distribution for running the award-winning Kodi software on popular mediacentre hardware. LibreELEC is a conservative fork of the popular OpenELEC project with a stronger focus on pre-release testing and post-release change management. Further information on the project can be found on the LibreELEC website.
Issues & Support
Please report issues via the LibreELEC forum: Bug Reports. Please ask support questions in the LibreELEC forum: Help & Support or ask a member of project staff in the #libreelec IRC channel on Freenode.
Donations
Contributions towards current project funding goals can be sent via PayPal to donations@libreelec.tv
License
LibreELEC original code is released under GPLv2.
Copyright
As LibreELEC includes code from many upstream projects it includes many copyright owners. LibreELEC makes NO claim of copyright on any upstream code. However all original LibreELEC authored code is copyright LibreELEC.tv. Patches to upstream code have the same license as the upstream project, unless specified otherwise. For a complete copyright list please checkout the source code to examine license headers. Unless expressly stated otherwise all code submitted to the LibreELEC project (in any form) is licensed under GPLv2 and copyright is donated to LibreELEC.tv. This approach allows the project to stay manageable in the long term by giving us freedom to maintain the code as part of the whole without the management overhead of preserving contact with every submitter, e.g. GPLv3. You are absolutely free to retain copyright. To retain copyright simply add a copyright header to each submitted code page. If you submit code that is not your own work it is your responsibility to place a header stating the copyright.