-
Lucas Russo authored
All of the SMIOs are now spawned by the SDB engine. So, if we want to avoid spawning a known module or something else, we must create a way to do so. Like a config file supporting blacklisted modules.
26607410
All of the SMIOs are now spawned by the SDB engine. So, if we want to avoid spawning a known module or something else, we must create a way to do so. Like a config file supporting blacklisted modules.
Name |
Last commit
|
Last update |
---|---|---|
cfg | Loading commit data... | |
doc/img | Loading commit data... | |
examples | Loading commit data... | |
foreign | Loading commit data... | |
include | Loading commit data... | |
kernel/pcie-driver | Loading commit data... | |
linker | Loading commit data... | |
scripts | Loading commit data... | |
src | Loading commit data... | |
tests | Loading commit data... | |
.gitignore | Loading commit data... | |
.gitmodules | Loading commit data... | |
.travis.yml | Loading commit data... | |
.ycm_extra_conf.py | Loading commit data... | |
COPYING | Loading commit data... | |
Makefile | Loading commit data... | |
README.md | Loading commit data... | |
ci_build.sh | Loading commit data... | |
compile.sh | Loading commit data... | |
run_valgrind.sh | Loading commit data... | |
valgrind.supp | Loading commit data... | |
version.sh | Loading commit data... |