The Driver Manager is responsible for enumerating, loading, and managing the life cycle of device drivers. Driver Manager also vends the /dev directory to the rest of the system so that others can access drivers.
Driver Manager is built and run in every product. It is launched on startup.
If you're looking for running an isolated Driver Manager for testing, please see isolated_devmgr.
When running Driver Manager there are some commandline options that can change Driver Manager's behavior. Normally these are set in the CML file when Driver Manager is run as a component, or through isolated Driver Manager for testing.
Load drivers from this directory. Can be specified multiple times to search multiple directories. If this is not defined, the default will be used.
Load a driver with this path. The specified driver does not need to be in a driver_search_path directory.
Connect the stdout and stderr file descriptors for this program to a debuglog handle acquired with fuchsia.boot.WriteOnlyLog.
Do not exit Driver Manager after suspending the system.
The path prefix for binaries, drivers, libraries, etc. This defaults to /boot/
Use this driver as the sys_device driver. If nullptr, the default will be used.
Use the default loader rather than the one provided by fshost.
Use the Driver Runner and launch this driver URL as the root driver.
The behavior of Driver Manager can also be changed by several kernel commandline options. Please look at the list of kernel commandline options and look for the options that start with devmgr.*