Closed eliasbakken closed 2 years ago
I think in order to keep the permutations to a minimum, we let u-boot load one dtb file for all revisions. u-boot does not need any revision specific initialization. The dtb file can be a symlink to the revision specific file. For the A5 to A6 transition, this should allow boards to boot even though the revision is wrong, allowing the user to change it after a boot.
Merged in master. Rev A6 has been tested, A5 has not.
Rev A6 introduces some hardware changes compared to A5 that needs to be handled by Klipper. This needs to be supported by Refactor.