dave
/
gary
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

vram/VRAM: only expect a response on reads 

The VRAMCore doesn't generate responses for writes, so demanding one here
deadlocks the port the first time it writes something.
This commit is contained in:
David Anderson 2024-09-14 16:40:14 -07:00
parent e021e7d356
commit 65d13a0e50
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
vram/VRAM.bsv
View File

@ -44,8 +44,11 @@ module mkArbitratedVRAMServers(VRAMServer ram, MemArbiter#(n, VRAMAddr) arb, Vec
(* fire_when_enabled *) (* fire_when_enabled *)
rule submit (awaiting_response[1] matches tagged Invalid); rule submit (awaiting_response[1] matches tagged Invalid);
let port = arb.granted_port(); let port = arb.granted_port();
ram.request.put(requests[port].first); let req = requests[port].first;
ram.request.put(req);
requests[port].deq(); requests[port].deq();
// Only reads generate a response.
if (req.data matches tagged Invalid)
awaiting_response[1] <= tagged Valid port; awaiting_response[1] <= tagged Valid port;
endrule endrule