az0re has quit [Remote host closed the connection]
anuejn has quit [Remote host closed the connection]
anuejn has joined #symbiflow
az0re has joined #symbiflow
damo22 has joined #symbiflow
citypw has quit [Ping timeout: 240 seconds]
citypw has joined #symbiflow
citypw has quit [Remote host closed the connection]
citypw has joined #symbiflow
enriq has joined #symbiflow
_whitelogger has joined #symbiflow
OmniMancer has joined #symbiflow
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
proteusguy has quit [Ping timeout: 258 seconds]
enriq has quit [Ping timeout: 244 seconds]
proteusguy has joined #symbiflow
enriq has joined #symbiflow
enriq has quit [Ping timeout: 260 seconds]
enriq has joined #symbiflow
damo22 has left #symbiflow [#symbiflow]
az0re has quit [Ping timeout: 240 seconds]
OmniMancer has quit [Quit: Leaving.]
OmniMancer has joined #symbiflow
OmniMancer has quit [Client Quit]
az0re has joined #symbiflow
enriq has quit [Ping timeout: 272 seconds]
enriq has joined #symbiflow
<sf-slack>
<mbpeterson70> Where did feature names originally come from? I'm not sure exactly sure how to word this, but were those decided purely from observation/need basis or were features names copied directly from bel properties and other properties in Vivado?
citypw has quit [Ping timeout: 240 seconds]
<litghost>
A mix. When there is a clear name, like a site pip or pip, then the name is straightforward. Same with straight forward parameters. There are some instances that are as needed.
az0re has quit [Remote host closed the connection]