<kristianpaul> If i'm sending data from a 80Mhz clock to a 16Mhz one, 3 flip flops should be okay for the clock domain sync, isnt??
<wolfspraul> how many frames per second does Milkymist render with right now?
<lekernel> something like 24
<kristianpaul> how many bits for color?
<lekernel> 16
<kristianpaul> and jsut to confirm resolution for render is 800x600 right?
<lekernel> it's 640 atm
<kristianpaul> (atm), this is limited by ADC chip?7
<lekernel> no by fpga design
<kristianpaul> DAC**
<kristianpaul> ok
<lekernel> dac can do 1280x1024 60 fps 24bpp
<lekernel> if you want render at this performance level, jfdi
<lekernel> I think it's technically feasible, with a lot of work though
<kristianpaul> we can go to then moon!, jfdi :-)
<kristianpaul> kidding
<kristianpaul> lekernel: minimac2_psync.v line 28, can you give me a hint doing that  level <= ~level ?
<wolfspraul> 16 bits per pixel, right?
<kristianpaul> maybe two signal changes are closer together??
<lekernel> wolfspraul, yes
<wolfspraul> ok so 640x480, 16bpp, 24fps
<wolfspraul> great, thanks
<kristianpaul> sure i know is cross clock domain, but i wast aware if this kind of implementation..
<kristianpaul> reads
<lekernel> wolfspraul, this is hopefully subject to change with FPGA design upgrades, so don't write it all over the marketing material
<lekernel> kristianpaul, the full minimac2_psync is well explained on the fpga4fun website
<kristianpaul> ok
<wolfspraul> no worries. first I need to understand where it is today, what is realistic with updates, what is the theoretical maximum of the current hardware
<wolfspraul> that's important in many ways, for customers, also for potential contributors, etc.
<wolfspraul> all fine, I think it's all great
<lekernel> if we get to do the "pro" version i'll probably make a new soc architecture to support 30bpp 1280x1024 everywhere (or something like that)
<lekernel> with improvements such as switching to myhdl, new bus architectures, faster memory controller, faster texture mapping unit, multiple LM32 cores, etc.
<lekernel> as I said, lots of work
<kristianpaul> (myhdl), :o
<kristianpaul> "get to do the "pro"" you mean, basically is a funding problem?
<lekernel> partly, it's also a problem of finding customers for it
<kristianpaul> just to be sure, that 'pro' word scare me a bit from before projects i know ;)
<kristianpaul> sure
<kristianpaul> yeah, sure you are the experts about recomended specs for VJing stuff
<kristianpaul> ha, flags i missed that part :-)
<mumptai> hi
<lekernel> hi
<GitHub143> [milkymist] sbourdeauducq pushed 1 new commit to master: http://bit.ly/pKALxU
<GitHub143> [milkymist/master] Update README - Sebastien Bourdeauducq
<GitHub184> [milkymist] sbourdeauducq pushed 1 new commit to master: http://bit.ly/rhXNY7
<GitHub184> [milkymist/master] Update headers - Sebastien Bourdeauducq
<GitHub23> [milkymist] sbourdeauducq pushed 1 new commit to master: http://bit.ly/ojj6rG
<GitHub23> [milkymist/master] Bump version number - Sebastien Bourdeauducq
<GitHub150> [milkymist] sbourdeauducq pushed 1 new commit to master: http://bit.ly/nZH6tV
<GitHub150> [milkymist/master] fmlmeter: add memory address capture support - Sebastien Bourdeauducq