sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
_whitenotifier-e has joined #m-labs
<_whitenotifier-e> [nmigen] adamgreig opened pull request #21: Give the top level scope a name to fix vcd file production - https://git.io/fh3h0
<_whitenotifier-e> [nmigen] whitequark commented on pull request #21: Give the top level scope a name to fix vcd file production - https://git.io/fh3hu
<_whitenotifier-e> [nmigen] whitequark closed pull request #21: Give the top level scope a name to fix vcd file production - https://git.io/fh3h0
<_whitenotifier-e> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/fh3hz
<_whitenotifier-e> [m-labs/nmigen] adamgreig 560bb00 - Give the top level scope a name to fix VCD hierarchy.
<_whitenotifier-e> [nmigen] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/m-labs/nmigen/builds/475849980?utm_source=github_status&utm_medium=notification
mumptai has quit [Quit: Verlassend]
<_whitenotifier-e> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/475850269?utm_source=github_status&utm_medium=notification
<_whitenotifier-e> [nmigen] Success. 80.53% (+0%) compared to a2b04d7 - https://codecov.io/gh/m-labs/nmigen/commit/560bb007cc3c7e5921ac353311dddb49f5da180e
<_whitenotifier-e> [nmigen] Success. 100% of diff hit (target 80.53%) - https://codecov.io/gh/m-labs/nmigen/commit/560bb007cc3c7e5921ac353311dddb49f5da180e
<sb0> whitequark: it was mentioned a few times and you were supposed to run satman on the rtm
<sb0> $ bloaty artiq_sayma_rtm/software/satman/satman.elf -d compileunits
<sb0> bloaty: Unknown ELF machine value: 92'
<whitequark> yeah, it needs a small patch to add openrisc support
<whitequark> let me remember what I put there...
<whitequark> ah found it https://hastebin.com/izenixeteg.cpp
<whitequark> that's basically a stub. I don't know why it even wants capstone, it doesn't do disassembly
futarisIRCcloud has joined #m-labs
<sb0> whitequark:
<sb0> $ bloaty /home/sb/artiq_sayma_rtm/software/satman/satman.elf -d compileunits
<sb0> bloaty: short DWARF compilation unit
_whitelogger has joined #m-labs
zng has quit [Quit: ZNC 1.8.x-nightly-20181211-72c5f57b - https://znc.in]
zng has joined #m-labs
_whitelogger has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] sbourdeauducq closed issue #792: IOSERDES TTLs for Kintex Ultrascale https://github.com/m-labs/artiq/issues/792
<GitHub-m-labs> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/6e43c411038c...b5501aaf0085
<GitHub-m-labs> artiq/master 66b3132 Sebastien Bourdeauducq: sayma_amc: fix RTIO TSC instantiation
<GitHub-m-labs> artiq/master b5501aa Sebastien Bourdeauducq: firmware: program I2C switch on Sayma RTM
_whitelogger has joined #m-labs
rohitksingh has quit [Ping timeout: 244 seconds]
<bb-m-labs> build #2196 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2196
rohitksingh has joined #m-labs
<bb-m-labs> build #2197 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2197
<bb-m-labs> build #982 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/982
<bb-m-labs> build #2792 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2792
rohitksingh has quit [Ping timeout: 240 seconds]
rohitksingh has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh has quit [Ping timeout: 258 seconds]
<whitequark> sb0: ok i'll look
rohitksingh has joined #m-labs
cr1901_modern1 has joined #m-labs
cr1901_modern has quit [Ping timeout: 258 seconds]
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined #m-labs
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh has joined #m-labs
<GitHub-m-labs> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/migen/commit/fd23e4fb1e3745e0274a264f03d9175b2d23aa06
<GitHub-m-labs> migen/master fd23e4f Sebastien Bourdeauducq: sayma_rtm: fix si5324_clkin IOSTANDARD
<GitHub-m-labs> [misoc] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/misoc/compare/734fa4c08d78...1bf426ae0dfd
<GitHub-m-labs> misoc/master 8a02de8 Sebastien Bourdeauducq: support single-BRAM SoC with no external RAM
<GitHub-m-labs> misoc/master 1bf426a Sebastien Bourdeauducq: sayma_rtm: use single BRAM
<GitHub-m-labs> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/321748882404a782f0a93c14df8998dbdc537db7
<GitHub-m-labs> artiq/master 3217488 Sebastien Bourdeauducq: add Sayma RTM DRTIO target
<bb-m-labs> build #458 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/458
<bb-m-labs> build #362 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/362
kc5tja has joined #m-labs
<bb-m-labs> build #2198 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2198
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
<kc5tja> Hello folks. I'm planning on exploring the use of Migen for working on my Kestrel-3 project's main processor and TileLink-compatible interconnect. The docs that were online were great, but I found a number of the tutorials were old and the code examples no longer worked as written. After some tweaking, they worked great though.
<kc5tja> I'm thinking, is it OK for me to "overhaul" the documentation? Maybe move one or two of the tutorials into the user's guide, modernizing the code examples to the latest migen release in the process?
<key2> migen or nmigen ?
<bb-m-labs> build #2199 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2199
<kc5tja> I was using migen. I am aware of nmigen, but since it's still in flux, I decided to avoid it until it was more or less stable.
<kc5tja> What would be the benefits of using nmigen over migen?
hartytp has joined #m-labs
<kc5tja> key2: Thanks, already reviewed it as it's linked to from migen's website. My query was in respect to improving migen's own documentation though.
<whitequark> kc5tja: the features that are already in nmigen are rather unlikely to change at this point
<hartytp> kc5tja: fwiw, any improvement in (n)migen's documentation would be amazing
<whitequark> with the exception of the things explicitly called out in the bug tracker
<whitequark> (mostly just .get_fragment() will be renamed)
<whitequark> the benefits of nmigen are numerous; in general, the user experience is far nicer
<whitequark> migen also contains a number of outstanding bugs related to edge cases in memories and elsewhere
<whitequark> that are not present in nmigen by design
<kc5tja> hmm, OK, thanks. I'll download and play with nmigen today then.
<hartytp> whitequark: agreed. Many of the quirks that I would have liked to have seen documented in migen are not present in nmigen
<kc5tja> Glad I asked before I started any significant development work. :)
<hartytp> would be great to see some docs for things like records (some examples that illustrate what problem they're designed to solve and how to use them)
<hartytp> clockdomainrenamers etc
<adamgreig> any docs at all in fact :p
<whitequark> hartytp: there are examples in nmigen!
<hartytp> yes, I saw, that's good
<hartytp> but, an expanded user guide would also be really helpful
<kc5tja> re: records -- it was exactly this that motivated my desire to contribute, actually. Working with TileLink would be a nightmare without them.
<bb-m-labs> build #983 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/983
<bb-m-labs> build #2793 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2793
<hartytp> yes. I think a few lines in the UG about records (again, particularly, something explaining what problems they are intended to solve) etc would be a great supplement to the examples
<kc5tja> If people don't mind my asking a ton of stupid, silly, beginner-level questions, I'd be happy to spend some time providing some manner of documentation.
<whitequark> a good start would be porting migen's user guide to nmigen
<key2> :)
<adamgreig> maybe something like rtfd.org or other webhook could be set up to build docs+api ref from the git repo?
<hartytp> whitequark: are you still planning to move artiq to nmigen?
<whitequark> hartytp: sure. that was a part of what we discussed with sb0 when talking about nmigen.
<hartytp> ace
<hartytp> :)
<whitequark> yeah, i'll set up rtd for nmigen
<key2> whitequark: what's next on nmigen btw ?
<whitequark> key2: cr1901 is looking into replacing migen.build with edalize
<whitequark> there are some outstanding bugs on the tracker i'll fix
<whitequark> there is a need to port stuff like FIFOs
<whitequark> other than that it's done i think
<key2> k
<key2> so the gen basically
<key2> i mean the lib
<whitequark> yes
<adamgreig> would the platform stuff go in with the edalize build stuff?
<adamgreig> like an nmigen way to define board pinouts, 'connectors' maybe, and platform specific instances for io etc
<whitequark> I don't know yet
<adamgreig> the build and platform stuff from migen was super duper convenient for me, especially when migen already has your dev board as a platform
<adamgreig> still happier on balance with nmigen though
<whitequark> nmigen will gain the build and platform stuff for sure
<kc5tja> Oh, so platform stuff is not present in nmigen then?
<whitequark> not at the moment
<whitequark> it has some fairly severe design issues
<kc5tja> (sorry, was off reading RTD on how to use RTD.)
<whitequark> so it will need to be reworked, like everything else from migen, before appearing in nmigen
<kc5tja> Good to know -- less documentation to port. ;)
<adamgreig> also platform and build were quite tightly coupled in migen aiui
<whitequark> yes
<whitequark> in migen they were uh... organically grown
<whitequark> more than designed
<cr1901_modern> whitequark: It wasn't my plan to put board pinouts, etc w/ edalize stuff
<cr1901_modern> fwiw
<cr1901_modern> I think that should still be migen's responsibility
<adamgreig> does edalize know how to produce pcf files for each platform?
<adamgreig> or just how to poke the tools with existing files?
<cr1901_modern> the latter
<cr1901_modern> I'm not against redesigning how platform works, just that I think nmigen should still generate pcfs and leave the actual building to edalize
<whitequark> sure
hartytp has quit [Ping timeout: 256 seconds]
X-Scale has quit [Ping timeout: 245 seconds]
X-Scale` has joined #m-labs
X-Scale` is now known as X-Scale
lkcl has quit [Ping timeout: 245 seconds]
<_whitenotifier-e> [nmigen] sam-falvo opened pull request #22: Updated user guide introduction for nmigen. - https://git.io/fhszI
lkcl has joined #m-labs
<kc5tja> that'd be me making the PR. :) Off to get some lunch.
<_whitenotifier-e> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/476074824?utm_source=github_status&utm_medium=notification
<_whitenotifier-e> [nmigen] codecov[bot] commented on pull request #22: Updated user guide introduction for nmigen. - https://git.io/fhszr
<_whitenotifier-e> [nmigen] Success. 80.53% remains the same compared to 560bb00 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...27b69ee391e34039751e7103a86fcca344b1e007
<_whitenotifier-e> [nmigen] Success. Coverage not affected when comparing 560bb00...27b69ee - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...27b69ee391e34039751e7103a86fcca344b1e007
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsgJ
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsgU
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsgt
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsgq
rohitksingh has quit [Ping timeout: 268 seconds]
<kc5tja> I don't see where "ASIC Mode" appears in the introduction. What am I missing?
<_whitenotifier-e> [nmigen] sam-falvo synchronize pull request #22: Updated user guide introduction for nmigen. - https://git.io/fhszI
<kc5tja> Also, do we want to use nMigen everywhere, or just at the start of a sentence?
<_whitenotifier-e> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/476103208?utm_source=github_status&utm_medium=notification
<_whitenotifier-e> [nmigen] Success. 80.53% remains the same compared to 560bb00 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...df7b762ecd697c742dee5e44c9d3cf46b7e76433
<_whitenotifier-e> [nmigen] Success. Coverage not affected when comparing 560bb00...df7b762 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...df7b762ecd697c742dee5e44c9d3cf46b7e76433
<whitequark> 21:38 < kc5tja> I don't see where "ASIC Mode" appears in the introduction. What am I missing?
<whitequark> Migen offered some sort of mode for ASICs that does not do anything with register init values
<whitequark> nMigen does not
<whitequark> 21:42 < kc5tja> Also, do we want to use nMigen everywhere, or just at the start of a sentence?
<whitequark> I don't understand the question
<adamgreig> as opposed to `nmigen`
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsVY
<whitequark> everywhere, yeah
<whitequark> that's the name of the project
<_whitenotifier-e> [nmigen] sam-falvo reviewed pull request #22 commit - https://git.io/fhsVs
<_whitenotifier-e> [nmigen] sam-falvo reviewed pull request #22 commit - https://git.io/fhsVG
<_whitenotifier-e> [nmigen] sam-falvo reviewed pull request #22 commit - https://git.io/fhsVn
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsVc
<kc5tja> OK, will fix.
<_whitenotifier-e> [nmigen] sam-falvo reviewed pull request #22 commit - https://git.io/fhsVl
<_whitenotifier-e> [nmigen] sam-falvo synchronize pull request #22: Updated user guide introduction for nmigen. - https://git.io/fhszI
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhsVa
<_whitenotifier-e> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/476107205?utm_source=github_status&utm_medium=notification
<_whitenotifier-e> [nmigen] Success. 80.53% remains the same compared to 560bb00 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...a9c7687c3cb527fb6e19cd6b84b510aba5a8ed02
<_whitenotifier-e> [nmigen] Success. Coverage not affected when comparing 560bb00...a9c7687 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...a9c7687c3cb527fb6e19cd6b84b510aba5a8ed02
<mithro> whitequark: Will you be taking contracting work to port things from migen to nmigen?
<whitequark> mithro: it's possible; i would be especially interested in funding for a tool that automatically ports migen code to nmigen
<whitequark> but this needs a feasibility study first
<mithro> whitequark: That might be something I'm interested in -- I would be very interested in something along the lines of a migen linter / pep8 type thing too....
<whitequark> okay, i'll take that into account
<mithro> whitequark: The new "with XXX" syntax should be more pep8 friendly anyway, right?
<whitequark> yes
<_whitenotifier-e> [nmigen] sam-falvo reviewed pull request #22 commit - https://git.io/fhswb
<_whitenotifier-e> [nmigen] whitequark reviewed pull request #22 commit - https://git.io/fhswp
<_whitenotifier-e> [nmigen] sam-falvo synchronize pull request #22: Updated user guide introduction for nmigen. - https://git.io/fhszI
<_whitenotifier-e> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/476117022?utm_source=github_status&utm_medium=notification
<_whitenotifier-e> [nmigen] Success. 80.53% remains the same compared to 560bb00 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...aa70a356ccf98fcb28be0435fb91b5b28bef151d
<_whitenotifier-e> [nmigen] Success. Coverage not affected when comparing 560bb00...aa70a35 - https://codecov.io/gh/m-labs/nmigen/compare/560bb007cc3c7e5921ac353311dddb49f5da180e...aa70a356ccf98fcb28be0435fb91b5b28bef151d
cedric has quit [Ping timeout: 272 seconds]