robotcontrol_modules.conf is bogus
Created by: mvduin
When testing a 4.19-ti kernel I noticed on my system that systemd-modules-load.service had failed at boot.
A quick inspection of the culprit, /etc/modules-load.d/robotcontrol_modules.conf
, revealed that this file is entirely pointless. All of the modules listed there are for drivers that are found based on of_device_id and they will be loaded automatically if and when they are needed (if compiled as module of course).
Indeed, after removing this file, all of the modules listed (apart from the two builtins) are still loaded during boot on 4.14-ti with cape-universal and remoteproc-pru enabled (to ensure there are devices that require these drivers).