[libre-riscv-dev] memory interface diagram woes

Luke Kenneth Casson Leighton lkcl at lkcl.net
Thu Apr 23 10:02:18 BST 2020


On Thursday, April 23, 2020, Jacob Lifshay <programmerjake at gmail.com> wrote:

> I had an idea for a memory interface design that I've been slowly
> working on for more than a week, though have not been able to draw it
> out adequately because I keep getting frustrated by the lack of nice,
> power-of-2 alignment features and support for structurally recursive
> diagrams in Dia and the lack of copy-paste when using physical paper.


doh :)

there is a reason why i write things out as diagrams (and why i look at
graphviz all the time).  they map easier in my head to gates, and as a
result it becomes possible to check that it hasn't any surprise pathways in
HW


> I'll try to write it out as text on the wiki tomorrow.


ok.


> It is a bit different than the design Luke came up with and I think it
> addresses several of that design's shortcomings.


ok i can grok that.

thanks for explaining jacob.




-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68


More information about the libre-riscv-dev mailing list