Rename port methods:

sendBlockSizeQuery() -> peerBlockSize()
recvBlockSizeQuery() -> deviceBlockSize()
After seeing how this gets used in practice, the
send/recv*Query names just don't make a lot of sense.

dev/io_device.cc:
mem/port.cc:
    sendBlockSizeQuery() -> peerBlockSize()
mem/port.hh:
    sendBlockSizeQuery() -> peerBlockSize()
    recvBlockSizeQuery() -> deviceBlockSize()

--HG--
extra : convert_revision : e96349fb443979b85899a5248bd7cd8665e23ef0

1 files changed, 5 insertions, 2 deletions

diff --git a/mem/port.hh b/mem/port.hh
index d7a0faba2..3098b663c 100644
--- a/mem/port.hh
+++ b/mem/port.hh
@@ -86,6 +86,9 @@ class Port
 
   protected:
 
+    /** These functions are protected because they should only be
+     * called by a peer port, never directly by any outside object. */
+
     /** Called to recive a timing call from the peer port. */
     virtual bool recvTiming(Packet &pkt) = 0;
 
@@ -109,7 +112,7 @@ class Port
         this function to be called, a DMA interface doesn't really have a
         block size, so it is defaulted to a panic.
     */
-    virtual int recvBlockSizeQuery() { panic("??"); }
+    virtual int deviceBlockSize() { panic("??"); }
 
     /** The peer port is requesting us to reply with a list of the ranges we
         are responsible for.
@@ -164,7 +167,7 @@ class Port
     /** Called by the associated device if it wishes to find out the blocksize
         of the device on attached to the peer port.
     */
-    int sendBlockSizeQuery() { return peer->recvBlockSizeQuery(); }
+    int peerBlockSize() { return peer->deviceBlockSize(); }
 
     /** Called by the associated device if it wishes to find out the address
         ranges connected to the peer ports devices.