<_whitenotifier-e>
[nmigen-boards] gkelly commented on pull request #146: butterstick: add board defn for r1.0 - https://git.io/JM7Pq
<_whitenotifier-e>
[nmigen-boards] gkelly commented on pull request #146: butterstick: add board defn for r1.0 - https://git.io/JM7PV
lf has quit [Ping timeout: 268 seconds]
lf has joined #nmigen
<_whitenotifier-e>
[nmigen-boards] TomKeddie commented on pull request #146: butterstick: add board defn for r1.0 - https://git.io/JM7SZ
<_whitenotifier-e>
[nmigen-boards] gkelly edited a comment on pull request #146: butterstick: add board defn for r1.0 - https://git.io/JM7Pq
Degi_ has joined #nmigen
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
bl0x has quit [Ping timeout: 268 seconds]
bl0x has joined #nmigen
emeb_mac has quit [Ping timeout: 252 seconds]
bl0x has quit [Ping timeout: 268 seconds]
bl0x has joined #nmigen
<bl0x>
Hi, can one so bel placement constraints or other such annotations in nmigen?
<bl0x>
use, of course
y__ has joined #nmigen
y__ has quit [Ping timeout: 256 seconds]
y__ has joined #nmigen
<d1b2>
<dragonmux> you can pass constraint attributes like those using Attrs() as part of a resource. If you're using an Instance then you can pass them as a suitable attribute (a_). Based on the use of the term bel, we guess you're using Xilinx parts - almost any constraint you need can be set in the XDC which has an additions section you can set up with your Platform
bvernoux has quit [Quit: Leaving]
bvernoux1 has quit [Quit: Leaving]
<vup>
you can also use the `Signal(whatever, attrs={"SOME_ATTRIBUTE":"SOMEVALUE"})` (or `somesignal.attrs` if you already have a signal) to attach attributes to signals
<_whitenotifier-e>
[nmigen-boards] TomKeddie commented on pull request #146: butterstick: add board defn for r1.0 - https://git.io/JMdpP