changeset ab05a080d7c5 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=ab05a080d7c5
description:
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 <ni...@cs.wisc.edu>
diffstat:
configs/example/fs.py | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 lines):
diff -r c5a2c5ef6e68 -r ab05a080d7c5 configs/example/fs.py
--- a/configs/example/fs.py Sat Jan 03 17:51:48 2015 -0600
+++ b/configs/example/fs.py Sat Jan 03 17:51:48 2015 -0600
@@ -236,8 +236,8 @@
drive_sys = makeLinuxX86System(drive_mem_mode, np, bm[1],
cmdline=cmdline)
elif buildEnv['TARGET_ISA'] == 'arm':
- drive_sys = makeArmSystem(drive_mem_mode, options.machine_type, bm[1],
- cmdline=cmdline)
+ drive_sys = makeArmSystem(drive_mem_mode, options.machine_type, np,
+ bm[1], options.dtb_filename, cmdline=cmdline)
# Create a top-level voltage domain
drive_sys.voltage_domain = VoltageDomain(voltage = options.sys_voltage)
_______________________________________________
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev
