ChanServ changed the topic of #nmigen to: nMigen hardware description language · code at https://github.com/nmigen · logs at https://freenode.irclog.whitequark.org/nmigen · IRC meetings each Monday at 1800 UTC · next meeting TBD
<_whitenotifier> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±1] https://git.io/JtgL9
<_whitenotifier> [YoWASP/nextpnr] whitequark f67afcb - Update dependencies.
revolve has quit [Read error: Connection reset by peer]
revolve has joined #nmigen
lf_ has joined #nmigen
lf has quit [Ping timeout: 260 seconds]
<_whitenotifier> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://git.io/Jtgq0
<_whitenotifier> [YoWASP/yosys] whitequark c74bbf9 - Update dependencies.
_whitelogger has joined #nmigen
_whitelogger has joined #nmigen
Bertl_oO is now known as Bertl_zZ
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #nmigen
aquijoule__ has joined #nmigen
aquijoule_ has quit [Ping timeout: 265 seconds]
Degi_ has joined #nmigen
Degi has quit [Ping timeout: 258 seconds]
Degi_ is now known as Degi
electronic_eel has quit [Ping timeout: 246 seconds]
electronic_eel has joined #nmigen
PyroPeter_ has joined #nmigen
PyroPeter has quit [Ping timeout: 256 seconds]
PyroPeter_ is now known as PyroPeter
revolve has quit [Read error: Connection reset by peer]
revolve has joined #nmigen
revolve has quit [Read error: Connection reset by peer]
revolve has joined #nmigen
emeb_mac has quit [Quit: Leaving.]
chipmuenk has joined #nmigen
lkcl has quit [Ping timeout: 276 seconds]
lkcl has joined #nmigen
petitionynd has joined #nmigen
petitionynd has quit [K-Lined]
hexastorm has joined #nmigen
<hexastorm> I am testing luna but still have issues (even after i build the new toolchain)... i know get  DriverConflict: Signal '(sig output__sdo__o)' is driven from multiple fragments: top, top.<unnamed #3>; hierarchy will be flattened
<hexastorm> okay ... it is a bug :-)
<hexastorm> checkout older git commit and there it works...
<whitequark> it's not necessarily a bug
<whitequark> that is a warning for a reason: you still get a valid design
<hexastorm> okay will test on hardware but if i checkout older git commit, i.e. git checkout hw-r0.2-154-ge49508f
<hexastorm> and then run the example I have no errors
<Sarayan> hexastorm: newer versions detecting more potential problems is not at all unusual
<Sarayan> happens all the time with compilers
<hexastorm> I did a test on physical hardware, master branch is not working and the older revision is working
<hexastorm> I also get warning when I build it /home/pi/projects/luna/luna/gateware/utils/cdc.py:42: DriverConflict: Signal '(sig output__sdo__o)' is driven from multiple fragments: top, top.<unnamed #3>; hierarchy will be flattened
<hexastorm>   output = signal.like(signal)
<hexastorm> Warning: No clocks found in design
<hexastorm> Warning: No clocks found in design
<hexastorm> I did build yosys, nextpnr and ice40 from git... still have the same errors..
<hexastorm> for trellis i used yowasp and also get errors..
<hexastorm> this is the test case I used https://github.com/hstarmans/FPGAG/blob/master/test/test_spi.py, note that the rest of the code i hot mess and ugly as hell :-)
lkcl has quit [Ping timeout: 276 seconds]
<hexastorm> i think project like nmigen and luna are really great... but I think you should consider using pep8 conventions, running flake8 and the like. Typically, package is contained in src folder etc..
<whitequark> the conventions used in nmigen are well thought out
<hexastorm> they are really well thought out.. but it still surprises me that you don't abide by pep8...
<Sarayan> "Why don't you change everything to adopt the latest fad?" - One of the questions I'm sure whitequark loves
<Sarayan> See also: build systems
lkcl has joined #nmigen
Bertl_zZ is now known as Bertl
<hexastorm> a lot of work went it to it.. code is great .. wouldn't be able to write it but all these wild card are a bit annoying .. this convention was made by guido van rossem in 2001. There is one defensible use case for a wildcard import, which is to republish an internal interface as part of a public API (for example, overwriting a pure Python
<hexastorm> implementation of an interface with the definitions from an optional accelerator module and exactly which definitions will be overwritten isn't known in advance).
hexastorm has quit [Quit: Ping timeout (120 seconds)]
Bertl is now known as Bertl_oO
<anuejn> Personally I am more than happy with the nmigen conventions :)
revolve has quit [Read error: Connection reset by peer]
revolve has joined #nmigen
tich has joined #nmigen
<tich> Good day!
balrog has joined #nmigen
<agg> I like the doc's suggestion to use "import nmigen as nm" if you don't want the glob import, which messes with my editor's limited static analysis
<agg> though I usually do just import Signal, Elaboratable, Cat, Module and friends explicitly anyway
DaKnig has quit [Ping timeout: 256 seconds]
DaKnig has joined #nmigen
DaKnig has quit [Changing host]
DaKnig has joined #nmigen
<DX-MON> *smh at above* pep8 arguably can't apply to a hardware description DSL as it was intended for software.. and there are several quite accessability-misguided things pep8 usually insists upon.. nMigen is doing just fine without it
<hell__> > Many projects have their own coding style guidelines. In the event of any conflicts, such project-specific guides take precedence for that project.
<modwizcode> yeah I was a bit weirded out by nmigen's conventions at first but they're all there for good reason
Sarayan has quit [Quit: bbl, hard drive fun]
pftbest_ has joined #nmigen
pftbest has quit [Read error: Connection reset by peer]
tich has quit [Ping timeout: 264 seconds]
<whitequark> agg: yeah, lots of valid reasons to not want globs in user code, such as if you don't just have nmigen code there.
Sarayan has joined #nmigen
<cr1901_modern> whitequark: Your BuildPlan strategy (dict that stores files as strings) came in handy in an unexpected way today: https://twitter.com/cr1901/status/1357558533647183874
<cr1901_modern> Run GUI, copy all the file outputs (which includes the actual command-line invocation) to a dictionary. Repeat 50 times, tweaking the radio/checkboxes. Store them all to a JSON file. Then use Jupyter notebook to get the full set of command-line arguments.
<modwizcode> whitequark: Any progress on my other cxxrtl patch btw?
emeb_mac has joined #nmigen
<Sarayan> reminds me I have to try it
<Sarayan> too many things at the same time :-)
<hell__> cr1901_modern: interesting
<agg> Cat(*sigs).any() should end up identical to reduce(operator.or, sigs), right?
<agg> except without having to import from functools and operator
<vup> agg: is sigs composed of only 1 bit signals?
<agg> good point, yes
<vup> then it should be identical
<vup> any uses a specialized cell and reduce not, so arguably the any variant could be easier on the synthesis tool
<agg> even better
DaKnig has quit [Ping timeout: 276 seconds]
<_whitenotifier> [nmigen] hellow554 commented on issue #572: Add option to suppress code generation comments - https://git.io/Jt2Un
<awygle> Morning
<agg> o/
<vup> morning :)
<_whitenotifier> [nmigen] hellow554 opened issue #590: How to derive the negative edge from a clock - https://git.io/Jt2kI
<_whitenotifier> [nmigen] hellow554 edited issue #590: How to derive the negative edge from a clock - https://git.io/Jt2kI
<_whitenotifier> [nmigen] hellow554 edited issue #590: How to derive the negative edge from a clock - https://git.io/Jt2kI
<_whitenotifier> [nmigen-boards] hellow554 opened issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2kM
<_whitenotifier> [nmigen] rroohhh commented on issue #590: How to derive the negative edge from a clock - https://git.io/Jt2kj
<_whitenotifier> [nmigen-boards] whitequark commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2Ie
<_whitenotifier> [nmigen-boards] hellow554 edited issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2kM
<_whitenotifier> [nmigen] whitequark commented on issue #590: How to derive the negative edge from a clock - https://git.io/Jt2Im
<_whitenotifier> [nmigen] rroohhh commented on issue #590: How to derive the negative edge from a clock - https://git.io/Jt2I4
<_whitenotifier> [nmigen-boards] hellow554 commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tt
<_whitenotifier> [nmigen-boards] hellow554 edited a comment on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tt
<_whitenotifier> [nmigen-boards] hellow554 edited a comment on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tt
<_whitenotifier> [nmigen-boards] whitequark commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tw
<_whitenotifier> [nmigen-boards] hellow554 commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tX
<_whitenotifier> [nmigen-boards] whitequark commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2tQ
<_whitenotifier> [nmigen-boards] hellow554 commented on issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2m4
<_whitenotifier> [nmigen-boards] hellow554 closed issue #141: Reason for duplication toolchain_program function - https://git.io/Jt2kM
<_whitenotifier> [nmigen] hellow554 commented on issue #590: How to derive the negative edge from a clock - https://git.io/Jt2YG
chipmuenk has quit [Quit: chipmuenk]
DaKnig has joined #nmigen
DaKnig has quit [Changing host]
DaKnig has joined #nmigen
jfng has joined #nmigen
revolve has quit [Read error: Connection reset by peer]
revolve has joined #nmigen
<whitequark> modwizcode: not yet, but i'll look into it soon
pftbest_ has quit [Remote host closed the connection]
bvernoux has quit [Quit: Leaving]
pftbest has joined #nmigen
pftbest has quit [Remote host closed the connection]
pftbest has joined #nmigen
<modwizcode> okay