10:02 <mithro> https://github.com/SymbiFlow/prjxray/tree/master/fuzzers/018-clb-ram

10:02 <tpb> Title: prjxray/fuzzers/018-clb-ram at master · SymbiFlow/prjxray · GitHub (at github.com)

13:31 <mithro> https://github.com/Wren6991/asciiwave

13:31 <tpb> Title: GitHub - Wren6991/asciiwave: Turn WaveDrom timing diagrams into ASCII art (at github.com)

14:21 <mithro> duck2: ping?

14:31 <duck2> mithro: hello

14:32 <mithro> duck2: Just reminding you about our GSoC Mentor+Student meeting tonight?

14:33 <mithro> duck2: Wondering how your weekly report is going?

14:42 <duck2> mithro: i'm writing the report currently, shouldn't take long

14:42 <mithro> duck2: Great!

14:50 <mithro> mgielda: https://github.com/renode/renode/issues/37

14:50 <tpb> Title: Support MDIO with LiteEth · Issue #37 · renode/renode · GitHub (at github.com)

14:50 <mithro> duck2: When you have written it, please share it with me so I can take a look

14:51 <duck2> mithro: ok

14:51 <sf-slack2> <mgielda> @me1 thanks

18:00 <mithro> duck2: Have you seen https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/libs/libarchfpga/src/physical_types.h ?

18:00 <tpb> Title: vtr-verilog-to-routing/physical_types.h at master · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)

18:19 <duck2> mithro: I answered in https://docs.google.com/document/d/1GK7VX8aIBzE9rJXEk1AsYQAQus0wUt9SfyFBSEnPLrc/edit . (It sucks that google docs doesn't support code.)

18:19 <tpb> Title: difference.md - Google Docs (at docs.google.com)

23:03 <hackerfoo> https://www.cnx-software.com/2019/06/17/perf-v-fpga-risc-v-development-board/

23:07 <litghost> @hackerfoo/@elms: I've found another case where multiple FASM features need to be emitted on a mux, thinking about implementing: https://gist.github.com/litghost/e67519928c3f15a3b7258c448589bfea

23:07 <tpb> Title: gist:e67519928c3f15a3b7258c448589bfea · GitHub (at gist.github.com)

23:08 <litghost> Thoughts?

23:10 <hackerfoo> That works.

23:12 <hackerfoo> Another more verbose option is to just use multiple lines: SLICE_FF.Q[0] : AFF.ZRST\n SLICE_FF.Q[0] : AFF.ZINI\n SLICE_FF.Q[0] : LATCH\n

23:13 <hackerfoo> It might be easier to parse.

23:39 <elms> litghost: I'm fine with that. other option is `|` to represent ORing the features, but perhaps a list is best

23:54 <hackerfoo> `&` would be more logical, but either could cause confusion.