Skip to content

Commit

Permalink
Add missing port<=>memory comment
Browse files Browse the repository at this point in the history
  • Loading branch information
Jared Barocsi committed Jul 22, 2019
1 parent e60ec7c commit bb0ca05
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion documentation/memory.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ interfaces _only_.
* Input: `address`, the address of a piece of data in memory, aligned to 4-byte wide blocks.
* Input: `valid`, true when the address specified is valid
* Output: `good`, true when memory is responding with a piece of data (used to un-stall the pipeline)
- Port <=> Memory:
- Port <=> Memory: the interface between the memory port and the backing memory
* Input: `bus.response`, the return route from memory to a memory port. This is primarily meant for connecting to an AsyncMemIO's response output, and should not be connected to anything else in any circumstance (or things will possibly break)
* Output: `bus.request`, a DecoupledIO that delivers a request from a memory port to memory. This is primarily meant for connecting to an AsynMemIO's request input, and should not be connected to anything else

Expand Down

0 comments on commit bb0ca05

Please sign in to comment.