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>
Packages referencing variables defined in setup_toolchain such as CC, CXX,
AR, CFLAGS, LDFLAGS, HOST_CC etc. etc. must only reference these variables in
pre_build()/pre_configure()/pre_make() etc. functions, as the variables will not
be available when the package is sourced, but will be available after the call
to setup_toolchain() from scripts/build.
Setting mount_point_mode results in permanent changes of filesystem
permissions, trashing permissions users may have manually set up.
Udisks2 doesn't do that either so drop that option.
Signed-off-by: Matthias Reichl <hias@horus.com>
Creating an updates symlink to /storage/.config/firmware in the
kernel firmware directory makes it impossible to add firmware
overlays with an updates folder.
Furthermore bluez/hciattach only looks for firmware files directly in
the /lib/firmware directory and ignores the /lib/firmware/updates
directory. So adding BT firmware via .config/firmware didn't work.
Solve this by adding files from /storage/.config/firmware as the
last step in kernel overlays setup so firmware files from there
will show up directly under /lib/firmware and override other firmware
files installed by the system and kernel overlays.
Signed-off-by: Matthias Reichl <hias@horus.com>
Without this fix, the context-menu key on the OSMC remote will fail to work, and maps to the EPG (TV channel guide).
This is discussed in https://github.com/osmc/osmc/issues/478
Currently both eventlircd and kodi try to grab input devices
which leads to a nasty race. If kodi wins the race eventlircd
can't do the keycode to lirc translation and users are left
with non-working buttons like OK.
Setting the LIBINPUT_IGNORE_DEVICE udev property for input
devices handled by eventlircd prevents the race as libinput
will then ignore these devices and kodi won't try to grab them.
Signed-off-by: Matthias Reichl <hias@horus.com>
