Tweak to support the newer PS3 BD (with IR) remote which identifies differently.
Version 1
[ 142.524200] input: BD Remote Control as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:43/0005:054C:0306.0001/input/i$
[ 142.533894] sony 0005:054C:0306.0001: input,hidraw0: BLUETOOTH HID v1.00 Gamepad [BD Remote Control] on 00:00:00:00:00:00
-------------
Version 2
[ 7476.763657] input: Sony Computer Entertainment Inc BD Remote Control as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/bluetooth/hci0/hci0:11/0005:054C:0306.000A/input/input9
[ 7476.764266] sony 0005:054C:0306.000A: input,hidraw4: BLUETOOTH HID v1.10 Gamepad [Sony Computer Entertainment Inc BD Remote Control] on 00:00:00:00:00:00
this makes no sense and may stop systemd-tmpfiles-setup,
journald-flush, sshd, irserver from starting
===
Jan 18 18:23:03 openelec systemd[1]: Found ordering cycle on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-journal-flush.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on var-log-debug.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Breaking ordering cycle by deleting job systemd-journal-flush.service/start
===
units with DefaultDependencies=no should be always properly ordered.
- all files should be xx-*.conf
- kodi.conf should be last. it appends $PATH and $LD_LIBRARY_PATH
for addons. those are very important.
- busybox.conf should be right before kodi. it sets $HOME. nothing but
kodi is allowed to override whatever is set by busybox.conf
- addons.conf should be first, so if we allow addon specific
profile files, those should not be allowed to override env vars
or functions we depend on.
Function Compare didn't work with USB vendor/device ids >= 2^15 (ie 0x925d)
because the value read from the string was not handled as a signed short. Values
should be signed and compared as such.
The kernel hardcodes the path to the key instantiation callback binary
as /sbin/request-key, meaning that providing keyutils as a separate
binary in an addon is impossible. It might be possible to use a
dangling symlink, but the three binaries built from this package
are all around 20 - 30KiB. Additionally, the request-key binary
is useful for more than one protocol.
keyutils is the "new" way of handling both DNS name resolution
(necessary for e.g. cifs dfs referrals) and security credentials, thus
replacing e.g. the rpc.idmap daemon.
Signed-off-by: David Härdeman <david@hardeman.nu>
