Hi, POWER_SUPPLY_TECHNOLOGY and POWER_SUPPLY_VOLTAGE_MIN_DESIGN and some other parameters are hardcoded in the linux driver source, but they are not really used anywhere, so the issue is mostly cosmetic. The relevant parameters are all read from the devicetree...
As for which devicetree blob (dtb) is used (or rather passed to the kernel on boot), this is configured in the u-boot bootloader setup, check boot.cmd/boot.scr files for the load command. Basically u-boot has a function to identify the board from some distinct features (type and size of memory, SID register of the A64, ...) and then sets an environment variable for the u-boot process and for the load command that moves the dtb, initrd and kernel image into RAM...
As for which devicetree blob (dtb) is used (or rather passed to the kernel on boot), this is configured in the u-boot bootloader setup, check boot.cmd/boot.scr files for the load command. Basically u-boot has a function to identify the board from some distinct features (type and size of memory, SID register of the A64, ...) and then sets an environment variable for the u-boot process and for the load command that moves the dtb, initrd and kernel image into RAM...
Come have a chat in the Pine IRC channel >>
