my issue is with how sunxi-3.4 interacts with systemd. The device is /devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input1/event1. The problem is that the default configuration of udev (by Lennart Poettering himself) identifies a power button as such only if one of its parents devices is in the "acpi" subsystem.
I wonder if a change is needed in udev or in the kernel
the easy thing to do is blame udev and systemd!
has been blaming udev for almost a decade now
konradoo87 has joined #linux-sunxi
my immediate curiosity is to understand how the current tree of devices gets built, and eventually modify it. I spotted the "leaf" device name in the driver's code, but cannot understand how it gets linked to its parents.
libv: "I then also wanted proper printing, which could immediately be piped into
a dram_something.c file for u-boot." <- I think fexc can do that already
konradoo77 has quit [Ping timeout: 240 seconds]
muxator: ACPI is only very recently appearing on ARM, and only on ARM64 servers following SBSA
so the choiche of using systemd as init 1 in arch linux arm is more or less doomed...
oliv3r_ has joined #linux-sunxi
muxator: I think the kernel has some APM emulation thing you could use
maybe systemd likes that more?
Nyuutwo_ has joined #linux-sunxi
RaYmAn_ has joined #linux-sunxi
buZz__ has joined #linux-sunxi
libv: the tool behind the bin2fex/fex2bin symlinks