Of course on DietPi RPi images, all those files below /boot exist, just like on RPi OS. Note that our images differ in this regards from board to board. For RPi images, we use their official kernel build (with all overlays etc), and it requires all these files on a FAT partition strictly. So you can modify/setup it exactly like RPi OS. For Quartz64 we use an unmodified mainline kernel (with U-Boot and extlinux), hence here are the sources: https://git.kernel.org/pub/scm/linux/ker...ing-stable
Here is our workflow to build kernel, U-Boot and create a DEB package from it: https://github.com/MichaIng/DietPi/blob/...artz64.yml
As you can see, we use a custom defconf, so adding the two config keys there would be easy. Having a look at them:
Both "If unsure, say Y." means that those are enabled by default, AFAIK. But we can try defining them explicitly and see whether it helps.
EDIT: Okay, I added them, builds are running: https://github.com/MichaIng/DietPi/actio...6907978685
You can find the firmware-soquartz.deb package here, once finished: https://dietpi.com/downloads/binaries/testing/
Here is our workflow to build kernel, U-Boot and create a DEB package from it: https://github.com/MichaIng/DietPi/blob/...artz64.yml
As you can see, we use a custom defconf, so adding the two config keys there would be easy. Having a look at them:
Both "If unsure, say Y." means that those are enabled by default, AFAIK. But we can try defining them explicitly and see whether it helps.
EDIT: Okay, I added them, builds are running: https://github.com/MichaIng/DietPi/actio...6907978685
You can find the firmware-soquartz.deb package here, once finished: https://dietpi.com/downloads/binaries/testing/