 David Anderson
|
65d13a0e50
|
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.
|
2024-09-14 20:24:40 -07:00 |
|
David Anderson
|
23a78eee9e
|
vram/VRAM: a little more documentation tweaking
|
2024-09-08 23:44:45 -07:00 |
|
David Anderson
|
16af267ab6
|
vram/VRAM: tweak docs, remove unnecessary rule condition
|
2024-09-08 23:42:27 -07:00 |
|
David Anderson
|
1929bbe3cc
|
vram/VRAM: at last, a video RAM, with all the gubbins
|
2024-09-08 23:39:12 -07:00 |
|
David Anderson
|
2760bad965
|
vram: move VRAM to VRAMCore, in prep for arbitrated VRAM
|
2024-09-08 09:28:28 -07:00 |
|
David Anderson
|
b2b2c14009
|
vram/VRAM: finish the top-level VRAM module
Well, for now at least. It can build 112KiB and 128KiB memories that
seem to synthesize to something reasonable.
|
2024-09-07 16:04:21 -07:00 |
|
David Anderson
|
f7cb4b6ba2
|
vram/VRAM: early VRAM implementation
Only checked up to mkByteRAMArray, main VRAM still WIP
|
2024-09-06 16:11:55 -07:00 |