[Libre-soc-bugs] [Bug 50] nmigen pinmux

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=50

--- Comment #15 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to andrey from comment #13)

> The issue I'm finding is that I have a rough understanding of the abstract
> (and hardware) problem, but I don't understand the code/explanation. There
> are many classes/methods in many different files,

now you know why i set strict coding standards so that you can pull
up 12 xterms on-screen side by side.

> and I don't know what to focus on. 

this is why i said to focus on a tiny task (20 lines).  you then made it 5x
larger, hence why you are struggling.  wark :)


> They also look quite esoteric to me, and their purpose isn't
> obvious.

yes, sigh, not enough docstrings due to not enough time.
does not help that external dependencies are the same way.
only reason i can cope is i am used to it.

i also went through the same "err what the hell" thing.
i just hide it.

> So was what I wrote in "testing_stage1.py" not at all relevant to stage 1?

it was... if you want to increase the work needed for stage 1 from 20 lines
to about 100.

suggest this:

1) use dummy_pinset the original
2) enumerate the dict and create Resources using
   format in comment #10 and comment #12
3) create a Platform() and call its build function.

this is literally 20 lines of code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.