still "Permission denied"
This could be the cause of the issue. Wait for chewitt .
Official LE13 Test Images for Amlogic (Kodi-22)
-
chewitt -
May 19, 2024 at 7:03 AM -
Thread is Unresolved
-
-
I linked the LE wiki article with instructions for creating a custom keymap in post #192. LE does not run the Amlogic vendor kernel that CE/Odroid wikis are written for. If you continue to use the wrong instructions ..
And you cannot change permissions on /sys and /proc folders that are owned/managed by the kernel. That's basic Linux sysadmin knowledge. Again, whatever instructions you are following are not for the mainline kernel.
-
??
I have already created a custom keymap and my remote works fine (as long as the machine is running). The wiki article does not describe how to configure IR remote wakeup.
-
And you cannot change permissions on /sys and /proc folders that are owned/managed by the kernel. That's basic Linux sysadmin knowledge. Again, whatever instructions you are following are not for the mainline kernel.
OK, so why does that "wakeup" file exist, if at all?
-
The wiki article does not describe how to configure IR remote wakeup.
The IR wake code is hardcoded in the BL301 component of the boot firmware. ISTR that CE uses a custom version of BL301 source with some closed-source companion code to support external configuration. At some point I'll get around to investigating and then replicating something similar but a) done with open sources and mainline u-boot, b) upstreamed so everyone can benefit. I have a rather long to-do list at the moment though.
OK, so why does that "wakeup" file exist, if at all?
Because Google AI is crap and suggested modifying the device-tree to add wakeup-source; and thus the kernel now blindly exposes support for something that the hardware does not support being controlled from the kernel (it is hardcoded in BL301).
