The indicator string is used to specify the string that is in the overlay listing when the driver is loaded and this isn’t necessarily the same as the string in the command string, which is the command to install the driver with any parameters that are needed.
You can run this program without having to change the config.txt file. The driver remains loaded until the next reboot and is reinstalled when you next run the program. Notice that the program has to have root permissions to be able to run sudo, even if the program isn’t being run as root.
The Device Tree is the modern way to specify the hardware configuration of a machine and to load and configure drivers.
The boot disk contains device trees for each of the different versions of the Pi and the loader selects the appropriate device tree for the Pi model that is booting.
The loader merges the device tree with the overlays listed in the config.txt file to produce a customized final device tree used to boot the system.
Overlays are fragments of the device tree which can be used to modify and add to the basic device tree.
Overlays can themselves be customized by specifying parameters.
When the loader parses the DT and applies all the overlays you have specified, the final DT is represented by the folders in /proc/overlay.
The DHT22 Humidity and Temperature Sensor provides an example of loading and customizing a driver.
A fairly recent innovation is the ability to load and customize drivers after the system has booted using the dtoverlay and dtparam commands.
You can easily write a program to load and configure missing drivers at runtime.
Dynamic loading of overlays doesn’t always work and unloading overlays, while possible, isn’t a good idea.
Andrew Ng's Machine Learning course from DeepLearning.AI on Coursera has been revamped and updated and its student ratings suggest it is better than ever. It now uses Python and introduces TensorFlow, [ ... ]