lekernel changed the topic of #milkymist to: Mixxeo, Migen, Milkymist-ng & other Milkymist projects :: Logs: http://en.qi-hardware.com/mmlogs
mumptai has quit [Ping timeout: 256 seconds]
gbraad has quit [Ping timeout: 256 seconds]
gbraad has joined #milkymist
gbraad has joined #milkymist
mumptai has joined #milkymist
kilae has joined #milkymist
sb0 has joined #milkymist
kyak has quit []
kyak has joined #milkymist
kyak has joined #milkymist
sb0 has quit [Quit: Leaving]
<playthatbeat> twitter wall working using tweetledee now
<playthatbeat> but still has the '3 lines' bug which is a shame - is there any way to deal with this?
<ysionneau> 15:46 < playthatbeat> twitter wall working using tweetledee now < nice!
sb0 has joined #milkymist
<ysionneau> in legacy milkymist soc, are lm32 interrupts active low? lm32 architecture manual says "A pending bit is set when the corresponding interrupt request line is asserted low". But by reading the milkymist and lm32 code, it seems interrupts are active high...
balrog has quit [Read error: Operation timed out]
balrog has joined #milkymist
balrog has quit [Read error: Connection reset by peer]
balrog has joined #milkymist
balrog has quit [Ping timeout: 264 seconds]
sb0 has quit [Ping timeout: 268 seconds]
sb0 has joined #milkymist
balrog has joined #milkymist
sh4rm4 has quit [Ping timeout: 240 seconds]
sh4rm4 has joined #milkymist
<sb0> they're always active high in milkymist
<sb0> they're active low in the original lm32, but active low signals inside FPGAs are a waste of time
<mumptai> it makes sense for some flash or anti-fuse fpgas
<sb0> those are even slower than slowtan6 and therefore of very limited use
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]]
<mumptai> ohh yes, they are slow
balrog has quit [Ping timeout: 276 seconds]
balrog has joined #milkymist
mumptai has quit [Quit: Verlassend]
sb0 has quit [Quit: Leaving]