lekernel changed the topic of #m-labs to: Mixxeo, Migen, MiSoC & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
sturmflut has quit [Quit: Leaving]
Bertl_zZ is now known as Bertl
<mithro>
Hi everyone, we (TimVideos) are just preparing for applying to GSoC - would anyone from Migen/MiSoC who is familiar with the full toolchain have time to mentor a student (probably PhD level) to do bring up of Migen/MiSoc on the miniSpartan6+ and Digilent Atlys board, plus reproducing the HDMI2USB firmware functionality using those tools?
<mithro>
sb0: if you have any suggestions on who would be a good person to poke (I'm assuming you don't have the time) I'd love to chat with them
stekern has quit [Ping timeout: 265 seconds]
stekern has joined #m-labs
<rjo>
sb0: what's the problem with building the bitstream?
<sb0>
mithro, maybe Florent Kermarrec, if he's up to it. this will involve sdram, and he knows how to get it to work.
<sb0>
rjo, it's slow, so it takes a while before the results (eg the coverage ones) are available
early has quit [Ping timeout: 252 seconds]
<rjo>
i can solve that byt running bitstream, bios+runtime and unittests as a matrix in parallel.
<rjo>
i think bitstream is very valuable because it tells you the timing, size, whether it fits etc.
<rjo>
did you turn of the automatic building?
<sb0>
a lot of the commits don't touch the bitstream...
<sb0>
yes, should I leave it on?
<sb0>
it doesn't do much atm as I'm mostly adding things to the GUI and other high level components that don't have unit tests
<rjo>
it is not really "continuous" integration is it is not automatic ;)
<rjo>
let me try doing the bitstream either in parallel (it doesn't hurt imho) or even only if there is a special flag in the commit-message.
<GitHub100>
[artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/bV9a
<ysionneau>
sb0: hummm setuptools does not seem to allow saying which optional feature you want from command line :/
<ysionneau>
maybe it will work if one uses pip to install artiq, let me try that...
<ysionneau>
sb0: ok , it seems we can do something like "pip3 install -e ." for normal (no GUI) install, and then "pip3 install -e .[GUI]" for with-GUI install . It will run setup.py ultimately but taking into accounts optional requirements
<ysionneau>
sb0: the downside is, by putting GUI requirements in "extra_require", then the normal "python ./setup.py [--user] install" will not install the GUI, if this is the expected behaviour then it's OK
antgreen has joined #m-labs
_florent_ has quit [Ping timeout: 265 seconds]
_florent_ has joined #m-labs
ysionneau has quit [Ping timeout: 256 seconds]
ysionneau has joined #m-labs
sturmflut has quit [Ping timeout: 240 seconds]
sturmflut has joined #m-labs
bentley` has joined #m-labs
<GitHub62>
[artiq] sbourdeauducq pushed 2 new commits to master: http://git.io/bKNd