<whitequark>
i think pip3 install nmigen-yosys *is* happening
<whitequark>
i just installed latest wasmtime and... it totally works? it's super fast? it's low latency? it doesn't do anything weird?
<cr1901_modern>
niiiiiiiice
<cr1901_modern>
whitequark: If you're adding paramiko, getting it to work on Windoze is kinda shitty because of the cryptography dependency. I _have_ done it before tho.
<cr1901_modern>
YMMV
<whitequark>
cr1901_modern: better options?
<whitequark>
I mean it's not like it's going to be a hard dependency or even the only option ever available
<whitequark>
it's just an optional remote builder you could use
<cr1901_modern>
I don't know any better options right now. If it's optional, then it's no problem.
<cr1901_modern>
I was just warning you ahead of time; if I _remembered_ how I built it, I would tell you
<whitequark>
there won't be any new mandatory dependencies for nmigen besides jinja2 and pyvcd
<cr1901_modern>
(and no, situation hasn't improved since upgrade to 10.)
<whitequark>
hell, I'd get rid of markupsafe if I could
<cr1901_modern>
Then nevermind for now. I'll play around w/ it when you add the code, and document my findings
<cr1901_modern>
because to reiterate- it _can_ be done. Just difficult.
<cr1901_modern>
Incidentally I've wanted this for a while now too, so ty ktemkin for bringing it up :P
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #nmigen
Vinalon has quit [Remote host closed the connection]
Vinalon has joined #nmigen
<cr1901_modern>
whitequark: Scrap what I said, paramiko actually works fine without _too_ much trouble (aside from ls/grep --color=auto, but whatever, that's irrelevant for nmigen).
<vup>
did issue #6 ever get anywhere? I would be especially interested in it in combination with Instances...
<vup>
also would usability improvements like coloring warning, errors, etc of the log output of for example vivado be in scope for nmigen?
Vinalon has joined #nmigen
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern1 has joined #nmigen
cr1901_modern1 has quit [Client Quit]
cr1901_modern1 has joined #nmigen
cr1901_modern1 has quit [Client Quit]
cr1901_modern has joined #nmigen
<whitequark>
vup: #6 is a lot of work and most of it is blocked by other infrastructural improvements that haven't been done yet
<whitequark>
coloring the vivado log was something migen did, but i'm not sure i would consider it in scope
thinknok has quit [Remote host closed the connection]
thinknok has joined #nmigen
thinknok has quit [Ping timeout: 265 seconds]
chipmuenk has joined #nmigen
chipmuenk has quit [Quit: chipmuenk]
<tpw_rules>
what's the best way to get a wide control word from a slow clock domain to a fast one? a 1 word fifo? some sort of sync protocol? it would be bad to observe it in the middle of changing it
<whitequark>
BusSynchronizer, but that isn't upstream yet
<whitequark>
if awygle is looking for more projects, there's an unfinished PR in the repo waiting for someone to push it to completion
<cr1901_modern>
whitequark: when you add the wasm version of yosys to nmigen, do you plan to add an override to use a separate (native or wasm) copy?
<whitequark>
yes, obviously
<whitequark>
i think the way it'll work is it will search for a native version, and if it's acceptable, use that, else try the python version, and if it's acceptable, use that
<whitequark>
and something like NMIGEN_USE_yosys=[python|native] to choose between them
<cr1901_modern>
There was a reason I asked that made me think it wasn't as "obvious", but by the time I reworded my message I forgot :/.
<whitequark>
so that it would specifically stick to one particular version you want and fail otherwise
<cr1901_modern>
ack
<whitequark>
the thing is that both the native verssion and the python version can be too old, in principle
<whitequark>
RTLIL can have incompatible changes and currently the RTLIL emitter is not parameterized with the expected Yosys version
<whitequark>
and I don't want to change it to be
Asuu has joined #nmigen
rohitksingh has quit [Ping timeout: 240 seconds]
Asu has quit [Ping timeout: 240 seconds]
<cr1901_modern>
I can't see why not offhand, but can the wasm yosys be used to synthesize code for the free toolchains as well? Or is it only meant to generate a tree ready for building?
<whitequark>
it sort of can
<whitequark>
if you want to download a ~90 MB PyPI package that spends a minute compiling the code before it even starts, and is 10 times slower at synthesis than native
<whitequark>
at least that's the kind of results i'm seeing right now
<cr1901_modern>
I thought you said wasm yosys was near native?
<cr1901_modern>
ah
<whitequark>
depends on what you're doing
<whitequark>
it was 2.5x slower than native when converting RTLIL to Verilog and CXXRTL
<whitequark>
it is not that good at running abc
<whitequark>
or SAT solvers
<awygle>
"if awygle is looking for more projects" oh dear
<awygle>
i'll... add the PR number to my todo list
<awygle>
that does sound useful and currently i'm using 1-word FIFOs for that purpose
<awygle>
also, good, uh.... "morning"
rohitksingh has joined #nmigen
<cr1901_modern>
It is morning in UGT
<whitequark>
morning!
<whitequark>
awygle: for the most part, you seemed to be interested in improving CDC stuff, which i also think you're better equipped to do than i am
<whitequark>
as it's very much one of those things with a lot of subtleties you only understand with extensive experience
<awygle>
i've somehow put you under a substantial misapprehension about both my skills and experience :p but sure i'll take it
<whitequark>
well, i found the design process wrt async FIFO reset feature very productive, for example