Iopsys being based on openwr't starts with clean OpenWRT sdk and then add a feed manifesto that overlays on top of standard OpenWRT. Making it a iopsys SDK. The manifesto adds new targets(board profiles), feeds and packages.
Iopsys takes responsibility for that a certain board type will be tested towards an iopsys release making it a more isp dependable product. Mainline openwr't packages have been forked to better support SOC's hardware abstraction. This to be able to handle the different non posix ways a chip vendor has chosen to support more advanced features that don't exist in standard linux.
Break out of how a iopsys supported board target is structured. Targets will be chosen by use of a tool in our board management called genconfig. Genconfig is part of the build system in the iopsys support scripts.
for example
./iop genconfig dg301
make