- if `/etc/flash-kernel/dtbs/`content is modified or erased for some reasons (new install ?) the u-boot setup and the kernel MTD usage will not be synchronized and the device will fail to boot.
- cmdline only "patch/override" the MTD partitions information. If the original DTB file provided by Debian is updated for some reasons (driver fixes), the kernel will still continue to use those fixes.
But I note during a flash-kernel it says:
~# flash-kernel
kirkwood-qnap: machine: QNAP TS419 family
Using DTB: kirkwood-ts419-6281.dtb
Installing /usr/lib/linux-image-5.10.0-25-marvell/kirkwood-ts419-6281.dtb into /boot/dtbs/5.10.0-25-marvell/./kirkwood-ts419-6281.dtb
Taking backup of kirkwood-ts419-6281.dtb.
Installing new kirkwood-ts419-6281.dtb.
So the source of the DTB is /usr/lib/linux-image-5.10.0-25-marvell
And in the file: /etc/flash-kernel/dtbs/README.dtbs is says:
DTB files installed in this directory will be used in preference to
the ones shipped with the kernel.
Which suggests to me that we could simply use a (local) DTB. ?
Then, rather than shuffling around all the bits of flash, we could simply run flash-kernel**
(** still need to resize NAS_Config ...mind you it's unclear we still need NAS_Config)
In Partitionning_details.md it says:
But I note during a flash-kernel it says:
So the source of the DTB is /usr/lib/linux-image-5.10.0-25-marvell
And in the file: /etc/flash-kernel/dtbs/README.dtbs is says:
Which suggests to me that we could simply use a (local) DTB. ?
Then, rather than shuffling around all the bits of flash, we could simply run flash-kernel**
(** still need to resize NAS_Config ...mind you it's unclear we still need NAS_Config)