<FL4SHK>
Does nMigen do anything weird if you have a module that doesn't use `m.d.sync`?
<dragonmux>
no, it gracefully handles that
<FL4SHK>
Good to hear.
<FL4SHK>
the issue I thought there was is actually not an issue
<FL4SHK>
I think, let me double check.
<FL4SHK>
Well, new problem. Somehow one of my signals is being driven from `d.comb` when I don't think I ever drove it from `d.comb`
<FL4SHK>
Ah, found the solution.
FL4SHK has quit [Ping timeout: 252 seconds]
<_whitenotifier-1>
[nmigen] H-S-S-11 opened issue #641: Attributes are not properly applied to IBUFDS (and possibly other primitives) in Xilinx platform - https://git.io/JoIRh
<_whitenotifier-1>
[nmigen] H-S-S-11 edited issue #641: Attributes are not properly applied to IBUFDS (and possibly other primitives) in Xilinx platform - https://git.io/JoIRh
emeb_mac has joined #nmigen
supersat has quit [Ping timeout: 246 seconds]
supersat has joined #nmigen
pie_ has quit [Quit: pie_]
pie_ has joined #nmigen
supersat has quit [Ping timeout: 260 seconds]
supersat has joined #nmigen
Sarayan has quit [Remote host closed the connection]
guan has quit [Ping timeout: 245 seconds]
anuejn has quit [Quit: No Ping reply in 180 seconds.]