diff options
author | lonkaars <loek@pipeframe.xyz> | 2024-05-14 16:31:56 +0200 |
---|---|---|
committer | lonkaars <loek@pipeframe.xyz> | 2024-05-14 16:31:56 +0200 |
commit | 8656e2c08162bc2a03e45f1f1a15c1d8273cd678 (patch) | |
tree | 5ecd8a35be54eaae078b0b932dbd8e2f9e0477ed | |
parent | dfbc93b69734af4ab3496bfae6ff6e62360a7522 (diff) |
more war tales
-rw-r--r-- | readme.md | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -43,6 +43,15 @@ `linux-image-` package from chroot prints lots of errors, but seems to work fine afterwards?). I have not tried using the IoT images as an installation base, as we were steered away from using these images due to slow boot times. +- Just use the decompiled device tree blobs instead of trying to compile the + device tree sources from the linux kernel. +- You can check if your modified device tree blob is working by `cat`-ing the + output of `/sys/firmware/devicetree/base/led_extern/label` and checking if it + matches with the label you set in the `led_extern` section of your device + tree source file. +- ZSH on the BeagleBone appears to print the prompt over command output if it + is not terminated with a newline character. You can work around this by using + `echo "$(cat ...)"` instead. # direct ethernet setup |