Easy Version Control rollback device-tree files

EasyOS on the PC has not been concerned with device-tree files, but they are a big thing on the ARM boards. They are in the boot partition, and are read at bootup. Information:

https://www.kernel.org/doc/html/latest/devicetree/usage-model.html

It is still a mystery to me how they work, but they are needed by the Raspberry Pi, and, as I discovered, getting the latest is important.

However, with Easy Version Control, if we roll back to an older version of Easy, we should really roll back the device-tree also. Ditto when roll forward.

The current device-tree files are in /boot/device-tree, which you can view in a running Easy. These are actually located inside easy.sfs. So, if roll back or forward to a different easy.sfs, then extract the device-tree files out of easy.sfs and copy them to the boot partition.

That is what Easy Version Control now does. The modified scripts are /usr/local/easy_version/easy-update and easy-version-control.

If you are running Easy 2.6, the "update" icon on the desktop will run /usr/local/easy_version/easy-update, which does not have this device-tree awareness, so will not copy the latest device-tree files to the boot-partition.
In that case, after upgrading to version 2.6.1, manually copy the files from /boot/device-tree to the boot-partition, replacing the old ones.

This manual step is only for 2.6. After that, every time you click "update", the device-tree files will update in the boot-partition automatically. 

Tags: easy