mem-ruby: Remove function that maps responses to a DMA engine
authorNikos Nikoleris <nikos.nikoleris@arm.com>
Tue, 2 Jan 2018 20:33:25 +0000 (21:33 +0100)
committerNikos Nikoleris <nikos.nikoleris@arm.com>
Thu, 11 Jan 2018 09:40:35 +0000 (09:40 +0000)
commit9737d93eb1d22946073d448c0c9200169f1a0b64
treeb3bd705b2ae3e5df3787d2d0965157ab83dbc57c
parentc6c222750d80b3f9235211f83e1115afb4e05432
mem-ruby: Remove function that maps responses to a DMA engine

The function map_Address_to_DMA was used to route responses to the
first (and assumed to be the only) DMA engine in the system. This
function is now unused as protocols handle responses and route them to
the right DMA engine.

Change-Id: I2fba913cf2f12321d1a1e38e7ee85bdf26b8a47a
Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/7162
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Maintainer: Jason Lowe-Power <jason@lowepower.com>
src/mem/protocol/RubySlicc_ComponentMapping.sm
src/mem/slicc/symbols/Type.py