Anthony Gutierrez 0d8d6e4441 arm: fix build_drive_system when not using default options ... when trying to dual boot on arm build_drive_system will only use the default values for the dtb file, number of processors, and disk image. if you are using the non-default files by passing values on the command line for example, or by making a new entry in Benchmarks.py, the build config scripts will still look for the default files. this will lead to the wrong system files being used, or the simulator will fail if you do not have them. Committed by: Nilay Vaish <nilay@cs.wisc.edu>		2015-01-03 17:51:48 -06:00
..
fs.py	arm: fix build_drive_system when not using default options	2015-01-03 17:51:48 -06:00
memtest.py	mem: Rename Bus to XBar to better reflect its behaviour	2014-09-20 17:18:32 -04:00
read_config.py	config: Add the ability to read a config file using C++ and Python	2014-10-16 05:49:37 -04:00
ruby_direct_test.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
ruby_mem_test.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
ruby_network_test.py	ruby: single physical memory in fs mode	2014-11-06 05:41:44 -06:00
ruby_random_test.py	ruby: interface with classic memory controller	2014-11-06 05:42:21 -06:00
se.py	config, kvm: Enabling KvmCPU in SE mode	2014-11-23 18:01:08 -08:00