<_whitenotifier-f>
[nmigen-boards] whitequark closed issue #63: UARTResource flow control signals direction mismatch for ICEStickPlatform - https://git.io/JfDBE
<_whitenotifier-f>
[nmigen-boards] whitequark closed pull request #65: Add role to UARTResouce and fix UART flow control pin inconsistencies - https://git.io/JfDxq
<_whitenotifier-f>
[nmigen/nmigen-boards] whitequark pushed 7 commits to master [+0/-0/±7] https://git.io/Jf9RV
<_whitenotifier-f>
[nmigen/nmigen-boards] ... and 4 more commits.
<_whitenotifier-f>
[nmigen-boards] whitequark commented on pull request #65: Add role to UARTResouce and fix UART flow control pin inconsistencies - https://git.io/Jf9Rw
<jeanthom>
Hi! Is there an easy way to check if NMIGEN_verbose is set in an Elaboratable?
<Lofty>
Use the Python environment tools
<Lofty>
e.g. os.environ["NMIGEN_verbose"]
<whitequark>
why do you want to check it?
<jeanthom>
Lofty, yep that seems the best option but I was curious if there was a more idiomatic way of doing it
<jeanthom>
whitequark, I want to add some debug information into some elaboratables. Say I want to encapsulate a PLL and calculate automatically its parameters, with NMIGEN_verbose=1 it would display its parameters, estimated output frequency, etc.
<whitequark>
I would suggest you go for the Python logging module
<whitequark>
the NMIGEN_verbose option is doing something different
<whitequark>
namely, it affects how the build scripts are generated, not how Python code runs
<whitequark>
of course, you can alwasys pass verbose="1" to the build() function based on your own parameter
<jeanthom>
Ok, I thought it was meant as a general verbose switch that would activate logging everywhere
<whitequark>
nope.
<_whitenotifier-f>
[nmigen/nmigen] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/Jf9uJ