Hi Andrea, - I'm always copying dtb's after compiling a custom kernel, be it mainline/next, over those contained in raspberrypi-firmware-dt package, for both testing purposes and under self-imposed impression that there could be issues/lack of compatibility between downstream dts's and upstream drivers. In either case overlays mostly work when present, meaning - I can use overlay to successfully disable internal bt module with dtoverlay=disable-bt-pi5 (speaking from memory since I tinkered with this when I first got a hold of pi, could double check again) but:
- cma-256 doesn't work when applied in a manner that Matthias enabled with his changes in raspberrypi-firmware package (dtoverlay=vc4-kms-v3d-pi5,cma-256), at least with upstream kernel+dtb and raspberrypi-firmware-dt contained overlays combo. Will try with everything from repos and I expect that will work, but at some point in time I guess that there won't be a need for downstream dt(b)s at all... - I'm expecting issues on this kind of setup for the time being, so no worries regarding security/integrity issues other than reporting those if I stumble upon any :) Thanks for your time and effort, you are all very supportive from the get-go, so engagement regarding testing just feels good/natural... BR, Ivan
