Forty-Bot has quit []
daveshah has joined #symbiflow
sorear has joined #symbiflow
_florent_ has joined #symbiflow
ovf has joined #symbiflow
adamgreig has joined #symbiflow
zkms has joined #symbiflow
zkms has quit [Client Quit]
zkms has joined #symbiflow
zkms has quit [Client Quit]
zkms has joined #symbiflow
zkms has quit [Client Quit]
zkms has joined #symbiflow
citypw has quit [Ping timeout: 250 seconds]
proteusguy has quit [Remote host closed the connection]
proteusguy has joined #symbiflow
OmniMancer has joined #symbiflow
storm has joined #symbiflow
storm is now known as Guest79203
<mithro> I didn't get to the make retry fix or getting Kokoro setup on Arch-Defs today
Guest79203 has quit [Ping timeout: 256 seconds]
OmniMancer has quit [Quit: Leaving.]
mkurc has left #symbiflow ["WeeChat 1.9.1"]
proteusguy has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Remote host closed the connection]
_whitelogger_ has joined #symbiflow
_whitelogger has joined #symbiflow
<elms> @litghost
<elms> oops early enter. fasm question: are routing and buffers designated destination.src? is that a convention or for a specific reason?
<litghost> Ya, it's tile.dest.src
<litghost> The original idea was potential to have enum like things, e.g. tile.dest = src
<litghost> where src is an enum of possibilities
<litghost> This is now being handled via the zero bit groups
<litghost> regardless, the convention has stayed
<elms> ok I can stick to it for iCE40. The icestorm organization tends to be src first.
<elms> icestorm is also using '/' in names. It's not supported in FASM currently. Any thoughts on adding as an allowed character?
<litghost> Example? I'm pretty sure we don't want to allow '/'
<elms> icesotrm has lutff_7/out and similar. I could replace with and make it lutff_7_out. is there a specific reason to disallow it? I could see it being slightly confusing, but wasn't sure if there is more
<litghost> The conventional replacement would be luff_7.out
<litghost> Depending on what lutff_7/out is
<litghost> Is it an output enable feature?
<litghost> Or a mux select?
<elms> it's the output wire from the 7th lutff
<elms> there are also lutff_[0-7]/in_[0-3]
<litghost> So lutff_7/out would appear in a FASM directive at all, unless you have a pip going to or from it?
<litghost> wouldn't*
<litghost> What would be an example feature directive using either the out or in wires?
<elms> I guess that't what I'm tying to make sure I follow convention. e.g. LOGIC_TILE_X6_Y8.LOCAL_G1_7.LUTFF_7/OUT
<litghost> Ya, that would be LOGIC_TILE_X6_Y8.LOCAL_G1_7.LUTFF_7_OUT
<litghost> I think it would be confusing to have '/' for 'Identifier' s
<litghost> It mixes hierarchy
<elms> sounds good. Thanks
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
<mithro> litghost: I don't think it makes sense to request my review on prjxray changes - I don't feel like I can give that meaningful review
<mithro> elms / litghost: Has is the status on a FASM style guide?
<mithro> I assume no progress?