There are two mechanisms to load overlays: the firmware (via config.txt), and dynamically loading
If you add a "dtoverlay=foo" line to config.txt, then the firmware loads and applies the overlay to the kernel before it starts booting. The kernel can't unload or list these as as far as it is concerned the overlay is part of the base DT file.
If you use "sudo dtoverlay foo" to load the overlay dynamically, then the kernel knows that an overlay has been loaded, and it can generally be unloaded again.
All documented under https://www.raspberrypi.com/documentati ... html#part3
If you add a "dtoverlay=foo" line to config.txt, then the firmware loads and applies the overlay to the kernel before it starts booting. The kernel can't unload or list these as as far as it is concerned the overlay is part of the base DT file.
If you use "sudo dtoverlay foo" to load the overlay dynamically, then the kernel knows that an overlay has been loaded, and it can generally be unloaded again.
All documented under https://www.raspberrypi.com/documentati ... html#part3
Statistics: Posted by 6by9 — Mon Dec 22, 2025 2:25 pm