lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs
xiangfu has joined #milkymist
hypermodern has joined #milkymist
jimmythehorn has quit [Ping timeout: 256 seconds]
azonenberg has left #milkymist [#milkymist]
_whitelogger has joined #milkymist
hypermodern has left #milkymist [#milkymist]
pablojavier has joined #milkymist
pablojavier has left #milkymist [#milkymist]
sh4rm4 has quit [Remote host closed the connection]
sh4rm4 has joined #milkymist
mumptai has joined #milkymist
azonenberg has joined #milkymist
mumptai has quit [Ping timeout: 252 seconds]
Martoni has joined #milkymist
Alarm has joined #milkymist
<GitHub91> misp/master ef45d06 Sebastien Bourdeauducq: Use new compiler-rt path
<GitHub91> [misp] sbourdeauducq pushed 1 new commit to master: http://git.io/1DKgww
<GitHub144> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/yOPqrw
<GitHub144> milkymist-ng/master 2059592 Sebastien Bourdeauducq: software/libcompiler-rt: add ctzsi2
lekernel_ has joined #milkymist
lekernel has quit [Ping timeout: 245 seconds]
<GitHub198> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/xURQmg
<GitHub198> migen/master 6fa3005 Sebastien Bourdeauducq: fhdl/verilog: tristate outputs are always wire
lekernel_ is now known as lekernel
stekern_ has joined #milkymist
stekern_ has quit [Ping timeout: 245 seconds]
antgreen has quit [Ping timeout: 245 seconds]
Zou has joined #milkymist
Gurty has quit [Ping timeout: 248 seconds]
Zou is now known as Gurty
gbraad has joined #milkymist
antgreen has joined #milkymist
<lekernel> /* The core i2c driver will automatically retry the transfer if the
<lekernel> * adapter reports EAGAIN. However, we find that bit-banging transfers
<lekernel> * generate spurious NAKs and timeouts. Retrying the transfer
<lekernel> * of the individual block a few times seems to overcome this.
<lekernel> * are susceptible to errors under a heavily loaded machine and
<lekernel> */
<lekernel> ah, linux ...
<Fallenou> ahah yes I saw that :)
<Fallenou> i2c in linux has a few quirks
<lekernel> ah and the nouveau driver loves broken DDCs. typically, it will disable the port until you reboot or suspend...
<Fallenou> fantastic !
Alarm has quit [Ping timeout: 245 seconds]
xiangfu has quit [Quit: leaving]
gbraad has quit [Ping timeout: 240 seconds]
gbraad has joined #milkymist
gbraad has quit [Changing host]
gbraad has joined #milkymist
sh4rm4 has quit [Remote host closed the connection]
sh4rm4 has joined #milkymist
gbraad has quit [Ping timeout: 245 seconds]
mumptai has joined #milkymist
antgreen has quit [Ping timeout: 257 seconds]
Alarm has joined #milkymist
antgreen has joined #milkymist
antgreen has quit [Ping timeout: 245 seconds]
jimmythehorn has joined #milkymist
_florent_ has joined #milkymist
<_florent_> Hi
<_florent_> just for info, after the de0 nano port
<_florent_> I'm starting working with milkymist-ng with the KC705
<_florent_> Nothing very insteresting to say for the moment because nothing is tested yet...
<_florent_> but I'll tell you when it will start working
<_florent_> for the moment there won't be a DDR3 controller
<_florent_> but we will have to discuss about that if some design can be share with your future M^3
<lekernel> great :)
<_florent_> Hi lekernel
<_florent_> for info the LM32 seems to work at at least 156MHz on the kintex
<_florent_> I've tried 200MHz but I was having timings errors....
<_florent_> 156 is probably not the max, but I haven't played with the mmcm for the moment
<Fallenou> very nice :)
<lekernel> hmm, weird, I'm quite sure I had 200
<lekernel> have you tried disabling some options (multipliers, divider ...)
mumptai has quit [Quit: Verlassend]
<_florent_> in fact 200 was ok for the cpu alone
<_florent_> but it must be close to 200, I was only having small timings issues on the multiplier
<_florent_> haven't try without
<_florent_> On the kc705 I'm going to use the milkymist-ng frame buffer + some color conversion module + the ADV7511 on the board
<_florent_> Do you have developped some simple code to test the frame buffer on the ng?
<_florent_> If so I'll be interested to test the frame-buffer --> color conversion --> ADV7511 chain
<larsc> _florent_: what are you running on the lm32?
<_florent_> for the moment , only the bios ;)
<_florent_> but I only wanted to know if some simple test code for the frame buffer existed for the bios
<Fallenou> you can flash the PONG demo instead of the BIOS for instance
<Fallenou> it makes simple use of the framebuffer
<_florent_> interesting!
<Fallenou> this is working on the M1 board
<_florent_> that's what I need I think
<Fallenou> you can play 1-player pong with the push buttons and VGA output
<_florent_> only a simple code that generate video
<_florent_> thanks
<Fallenou> you're welcome :)
<_florent_> I have to go
<_florent_> I'll send you a capture of the pong demo in 1080p when it will be working ;)
<_florent_> bye
<Fallenou> hehe very good :)
<Fallenou> a video ;)
<Fallenou> bye !
_florent_ has quit [Ping timeout: 245 seconds]
kyak has quit [Ping timeout: 264 seconds]
Alarm has quit [Quit: ChatZilla 0.9.90 [Firefox 19.0/20130215130331]]
kyak has joined #milkymist
kyak has quit [Changing host]
kyak has joined #milkymist
<lekernel> Fallenou, iirc the pong demo still uses the old SoC interface and should be loaded with netboot/flterm/flashboot (not flashed instead of the bios)
<Fallenou> the pong demo for the ml401 maybe
<Fallenou> but the pong demo for M1 is a replacement for the BIOS
<Fallenou> it initializes ddr controler etc
<Fallenou> it calls _sdram_init
lekernel has quit [Ping timeout: 260 seconds]
lekernel has joined #milkymist