From: Andreas Hansson Date: Wed, 25 Jan 2012 17:44:43 +0000 (-0500) Subject: MEM: Fix fs.py by specifying the range size rather than end X-Git-Tag: stable_2012_06_28~266^2~6 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=53c130bf2fdd4036b0988431c8cc32cfad06798e;p=gem5.git MEM: Fix fs.py by specifying the range size rather than end This patch fixes the currently broken fs.py by specifying the size of the bridge range rather than the end address. This effectively subtracts one when determining the address range for the IO bridge (from IO bus to membus), and thus avoids the overlapping ranges. --- diff --git a/configs/example/fs.py b/configs/example/fs.py index 11d7d43f0..08484559a 100644 --- a/configs/example/fs.py +++ b/configs/example/fs.py @@ -167,7 +167,7 @@ if options.caches or options.l2cache: test_sys.iocache.mem_side = test_sys.membus.port else: test_sys.iobridge = Bridge(delay='50ns', nack_delay='4ns', - ranges = [AddrRange(0, mem_size)]) + ranges = [AddrRange(mem_size)]) test_sys.iobridge.slave = test_sys.iobus.port test_sys.iobridge.master = test_sys.membus.port