01:47 <whitequark> let me rephrase: why is all diagramming software except for that one macos thing esden uses so unpleasant

05:46 <tnt> What was the reason to use an inverter rather than a negative edge FF ?

06:33 <whitequark> what would a negative edge ff give you?

06:35 <tnt> removes the need for the manual inverter all together unless I'm missing something.

06:36 <tnt> ( looking at https://github.com/GlasgowEmbedded/glasgow/pull/218/commits/514edece892db68cf5cb87b3b8a9c3bea5299929 atm )

06:37 <whitequark> tnt: it's a ripple counter

06:37 <whitequark> the inverter is there to make a TFF, not to make a negedge DFF

06:38 <whitequark> oh wait

06:38 <whitequark> there are *two* of them

06:38 <tnt> yeah ...

06:38 <whitequark> yeah you're right

06:38 <whitequark> sorry

06:38 <whitequark> was going off a previous version of PR

06:44 <tnt> Also, I was wondering if applying the clk_en to the first FF only wouldn't be better so you don't risk cutting of the ripple in the middle of a cycle.

06:44 <whitequark> yes, I think I mentioned that in the discussion earlier

06:44 <whitequark> it should definitely be applied only to first FF

06:45 <whitequark> not only because of that

06:45 <tnt> ah ok, sorry, didn't catch the whole backlog I guess.

06:45 <whitequark> but also because if you apply it to first FF, you can synchronize that to your input signal, so that you don't have a timing violation between C and E

06:45 <whitequark> since presumably E comes from the main gateware, and C is asynchronous to it

06:46 <whitequark> tnt: not really blaming you, it was a bit scattered

06:46 <whitequark> and I did tell Attie I'll walk them through this design

10:10 <yorick> gods, why is kicad so unpleasant to use <-- undiscoverable keybindings, mostly

10:11 <yorick> and apparently llvmpipe

11:06 <d1b2> <DX-MON> most of the time I've had that happen.. it's because I found I was stuck in Legacy mode again - clicking the Preferences menu option to switch to Modern Toolset (Accelerated) tools fixes the "ahhh, it's so unplesant"

11:07 <d1b2> <DX-MON> (so glad that whole.. mess.. is removed in what will be v6! no legacy, only modern)

12:40 <d1b2> <Attie> @whitequark / @tnt thanks for the comments, good points... I've fixed up the clock edge, and clock enable, and have reworked things so platform produces a single stage.

12:40 <d1b2> <Attie> I can't now, but I'll to test and push later

15:09 <_whitenotifier-f> [glasgow] attie synchronize pull request #218: applet.interface.freq_counter: implement basic frequency counter - https://git.io/JTCxQ

15:15 <_whitenotifier-f> [glasgow] attie synchronize pull request #218: applet.interface.freq_counter: implement basic frequency counter - https://git.io/JTCxQ

15:15 <_whitenotifier-f> [glasgow] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/github/GlasgowEmbedded/glasgow/builds/737104916?utm_source=github_status&utm_medium=notification

15:20 <_whitenotifier-f> [glasgow] attie synchronize pull request #218: applet.interface.freq_counter: implement basic frequency counter - https://git.io/JTCxQ

15:20 <_whitenotifier-f> [glasgow] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/github/GlasgowEmbedded/glasgow/builds/737108388?utm_source=github_status&utm_medium=notification

15:39 <_whitenotifier-f> [glasgow] Success. The Travis CI build passed - https://travis-ci.org/github/GlasgowEmbedded/glasgow/builds/737110618?utm_source=github_status&utm_medium=notification

21:53 <d1b2> <Attie> @whitequark - I've pushed my latest changes, they're ready for a look over when you have time