07:38 <cr1901_modern> sb0: Suppose I need to implement a latch to use in a Migen desgn. The easiest way to do this is to write a Verilog module for it. Now suppose I wanted to build my design using Migen's platform. >>

07:38 <cr1901_modern> What is the proper way to tell Migen that it needs to compile my custom latch module as well as the v file that Migen generates?

07:38 <sb0> what do you need a latch for?

07:40 <cr1901_modern> Combinational edge detector with hold- i.e. design detects active edge and then wants to see if the input signal transitioned back after a few clock cycles.

07:41 <sb0> the proper way is to add an abstract and platform-independent latch special to migen, plus platform specific implementation in mibuild

07:41 <sb0> but there is almost never a good reason to use a latch, which is why they are not supported

07:43 <cr1901_modern> I'm thinking whether I can implement the edge detector in a different way. I was trying to do sequential edge detector about an hour ago, but ran into a snag

07:43 <cr1901_modern> (which I don't remember anymore b/c of course I don't)

07:46 <cr1901_modern> More generally, looking at e.g. mibuild/xilinx/ise.py, line 162, it seems that migen will only permit one source file to be added- the one generated by migen itself. So if any Instances are used, it's not possible to use Migen to synthesize.

07:55 <cr1901_modern> I guess there hasn't been a pressing need to use multiple source files yet? :P

07:55 <cr1901_modern> Anyway, I'll work around it, or inherit from Special in my own design.

08:13 <sb0> we use multiple source files for mor1kx and lm32

08:13 <sb0> but i don't think you should use a latch.

09:08 <GitHub153> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/vTPYW

09:08 <GitHub153> artiq/master ea53ed1 Sebastien Bourdeauducq: gui: switch to Qt

09:34 <travis-ci> m-labs/artiq#150 (master - ea53ed1 : Sebastien Bourdeauducq): The build was broken.

09:34 <travis-ci> Build details : http://travis-ci.org/m-labs/artiq/builds/63619585

11:41 <mindrunner> how is the gpio classes supposed to work? can I easily control all my io-pins from software with it? dont i need tristates for that?

11:45 <whitequark> there are tristate gpio pins, iirc

11:45 <whitequark> you can set both value and direction

11:45 <whitequark> in some cases you can even enable PU/PD

11:46 <mindrunner> i dont really understand how to use GPIOInOut()

11:47 <mindrunner> i need to construct it with two signals

11:48 <mindrunner> i can just find an example where a pin is either used as input or oputput

11:48 <mindrunner> but not a universal gpio

11:49 <whitequark> wait, wrong channel, nevermind what I said

11:50 <whitequark> I thought you meant linux gpis

11:50 <whitequark> *gpios

11:51 <mindrunner> hehe

11:51 <mindrunner> okay

11:52 <ysionneau> GPIOInOut seems to just be a wrapper to register GPIOIn and GPIOOut

11:52 <ysionneau> but not for tristate

11:53 <mindrunner> yep

11:53 <ysionneau> for Tristate here is an example https://github.com/m-labs/migen/blob/master/examples/basic/tristate.py

11:54 <mindrunner> ok, so i need to set up a tristate for each pin and expose it to the software side with CSRs manually?

11:55 <ysionneau> also, some doc about Tri-state : https://migen.readthedocs.org/en/latest/fhdl.html#specials

11:55 <ysionneau> mindrunner: yes, you can do that

11:57 <mindrunner> cheers

14:08 <GitHub18> [artiq] fallen pushed 1 new commit to master: http://git.io/vTXAn

14:08 <GitHub18> artiq/master d78a275 Yann Sionneau: pxi6733: use a method as DoneEvent callback

14:37 <travis-ci> m-labs/artiq#151 (master - d78a275 : Yann Sionneau): The build is still failing.

14:37 <travis-ci> Build details : http://travis-ci.org/m-labs/artiq/builds/63655789

14:40 <GitHub108> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/vT1qr

14:40 <GitHub108> artiq/master cff999f Sebastien Bourdeauducq: doc: update mock modules

15:11 <travis-ci> m-labs/artiq#152 (master - cff999f : Sebastien Bourdeauducq): The build is still failing.

15:11 <travis-ci> Build details : http://travis-ci.org/m-labs/artiq/builds/63660711

15:32 <GitHub69> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/vT1Ko

15:32 <GitHub69> artiq/master 2570444 Sebastien Bourdeauducq: gui: add empty explorer and console docks

15:35 <GitHub27> [artiq] fallen pushed 1 new commit to master: http://git.io/vT1iL

15:35 <GitHub27> artiq/master 82ec931 Yann Sionneau: conda: add pyqtgraph+quamash dependencies/recipes and remove gbulb and cairoplot3

16:06 <travis-ci> m-labs/artiq#154 (master - 82ec931 : Yann Sionneau): The build was fixed.

16:06 <travis-ci> Build details : http://travis-ci.org/m-labs/artiq/builds/63668535

17:26 <GitHub65> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/vTM2c

17:26 <GitHub65> artiq/master d9c2513 Sebastien Bourdeauducq: gui: add explorer widgets

17:56 <travis-ci> m-labs/artiq#155 (master - d9c2513 : Sebastien Bourdeauducq): The build passed.

17:56 <travis-ci> Build details : http://travis-ci.org/m-labs/artiq/builds/63683206