Oops... some places in C++ explicitly ask for a "functional"
port. It would be better to move this to python IMO but for now I'll stick in a compatibility hack. --HG-- extra : convert_revision : a81a29cbd43becd0e485559eb7b2a31f7a0b082d
This commit is contained in:
parent
0305159abf
commit
aa5b595f39
1 changed files with 7 additions and 0 deletions
|
@ -336,6 +336,13 @@ PhysicalMemory::doFunctionalAccess(PacketPtr pkt)
|
||||||
Port *
|
Port *
|
||||||
PhysicalMemory::getPort(const std::string &if_name, int idx)
|
PhysicalMemory::getPort(const std::string &if_name, int idx)
|
||||||
{
|
{
|
||||||
|
// Accept request for "functional" port for backwards compatibility
|
||||||
|
// with places where this function is called from C++. I'd prefer
|
||||||
|
// to move all these into Python someday.
|
||||||
|
if (if_name == "functional") {
|
||||||
|
return new MemoryPort(csprintf("%s-functional", name()), this);
|
||||||
|
}
|
||||||
|
|
||||||
if (if_name != "port") {
|
if (if_name != "port") {
|
||||||
panic("PhysicalMemory::getPort: unknown port %s requested", if_name);
|
panic("PhysicalMemory::getPort: unknown port %s requested", if_name);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue