lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs :: Something to do? https://github.com/milkymist/bugs/issues
TachyonDev has quit [Read error: Connection reset by peer]
Jia has joined #milkymist
cladamw has joined #milkymist
xiangfu has joined #milkymist
jesse_ has quit [Ping timeout: 255 seconds]
jesse_ has joined #milkymist
cladamw_ has joined #milkymist
rejon_ has quit [Ping timeout: 272 seconds]
<cladamw_> except adding this 6.6 mm keep-out ring, I'll also keep J27 away from J21 about 1.5mm and still move to south 1.5 mm. The 0.32 mm you measured was traces in inner layers, but it's very nice a precaution discovery on using keep-out layer to clean. great.
<wpwrak> cladamw: great. maybe make the ring 7 mm in diameter. that way we can be sure it's large enough, even if something in the process changes slightly
<wpwrak> and perhaps you want to make all the 7 mm copper
<cladamw> how about we let all mounting holes with a total 6.5 mm copper and plus 0.5 extra keep-out layer ? then total is 7 mm
<cladamw> wpwrak, see my last sentences. :-) Is it okay to you? or you want 7 mm copper then we add extra 0.5 mm keep-out layer, so total 7.5 mm for mounting hole dia.
<wpwrak> roh suggested 7.0 mm minimum and likes 8 mm even better
<wpwrak> so 7.5 mm would fit that nicely :) do we have enough room ?
xiangfu has quit [Ping timeout: 240 seconds]
<cladamw> wpwrak, four corners I think there's no problems for 8 mm, i just want to let J27 with suitable dia and make it reserved to other routes, but overall i think J27 should be also okay for 8 mm in total.
<cladamw> wpwrak, so let's 7 mm for copper ring and 1 mm for extra keep-out ring
<wpwrak> yes, there should be enough room for 8 mm around J27
<wpwrak> hehe, cool. 7+1 = 8 then :)
xiangfu has joined #milkymist
xiangfu has quit [Ping timeout: 244 seconds]
xiangfu has joined #milkymist
<GitHub196> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/5ca97efb803b81e1ecc5acdcab2a57f81cbabeb4
<GitHub196> [board-m1/master] Misc.sch: removed text of "Placement (TP32, TP38-TP41) at the bottom of PCB." - Adam Wang
cladamw has quit [Quit: Leaving]
rejon_ has joined #milkymist
cladamw_ has quit [Quit: Ex-Chat]
voidcoder has quit [Read error: Connection reset by peer]
rejon_ has quit [Ping timeout: 272 seconds]
xiangfu has quit [Quit: Leaving]
cladamw has joined #milkymist
cladamw has quit [Ping timeout: 272 seconds]
cladamw has joined #milkymist
Gurty` has quit [Ping timeout: 265 seconds]
Gurty has joined #milkymist
elldekaa has joined #milkymist
sh4rm4 has quit [Ping timeout: 276 seconds]
sh4rm4 has joined #milkymist
cladamw has quit [Quit: Ex-Chat]
cladamw has joined #milkymist
jesse_ has quit [Ping timeout: 244 seconds]
cladamw has quit [Quit: Leaving]
lekernel_ is now known as lekernel
cladamw has joined #milkymist
wolfspra1l has joined #milkymist
wolfspraul has quit [Ping timeout: 245 seconds]
elldekaa has quit [Ping timeout: 244 seconds]
elldekaa has joined #milkymist
cladamw has quit [Ping timeout: 252 seconds]
cladamw has joined #milkymist
<GitHub139> [rtems-yaffs2] sebhub pushed 1 new commit to master: https://github.com/milkymist/rtems-yaffs2/commit/3294f1c700e52f1029f09b221143451ca3717263
<GitHub139> [rtems-yaffs2/master] rtems_yaffs: Update due to RTEMS API changes - Sebastian Huber
xiangfu has joined #milkymist
Jia has quit [Quit: Konversation terminated!]
elldekaa has quit [Ping timeout: 252 seconds]
<lekernel> now, writes ...
elldekaa has joined #milkymist
xiangfu has quit [Ping timeout: 272 seconds]
<wpwrak> "ddrrow" -> "Precharged". that what i call low-level control ;-)
<guyzmo> o/
<guyzmo> lekernel - hey, how are you doing ? :)
<guyzmo> lekernel - I had some adventures working the last version of milkymist (didn't know about the UI changes on right-click/esc keys :-S)
<guyzmo> lekernel - anyway, things have gone swell, though I only had less than ten vjs that went to see the workshop, and only ~4 did actually try to write FN patches
cladamw has quit [Ping timeout: 252 seconds]
<guyzmo> all were impressed by the realtime-ness of the stuff, but most of them said they don't want it, as their "usual" vj software can do everything that do the MM and more stuff, and they don't care that much about latency... while they did care about writing complicated lines of code to do stuff
<guyzmo> (one said "I prefer to stick with Puredata programming")
cladamw has joined #milkymist
<guyzmo> ...
voidcoder has joined #milkymist
<lekernel> so, does someone want to begin the development of the "rf reactable" surface?
<guyzmo> and last thing, they all said it's cool, but it'd be better if it could output HD !
<lekernel> this I'm on just now
xiangfu has joined #milkymist
<guyzmo> sweet :)
<guyzmo> so in the end, I'm quite sad to say that I don't think they will buy one
<guyzmo> to those guys
<guyzmo> but people working on VJ/video software were interested in the product to integrate it with they software so it can run and control stuff "blindly"
<lekernel> you mean resolume/modul8/... developers?
<lekernel> tell them they should instead consider running their software on a milkymist device :)
<guyzmo> nope, they weren't there, but the milumin dev guy was interested
<lekernel> milumin?
<guyzmo> it's a software that helps manage a whole stage scenography
<guyzmo> yup
<guyzmo> and there was also some guys working on a 3D mapping software
<guyzmo> that thought about it for a R&D project they're working on
<guyzmo> but anyway, I don't think that will end in real stuff
<guyzmo> and in the end, vision-r people were really nice
cladamw has quit [Quit: Ex-Chat]
xiangfu has quit [Remote host closed the connection]
<GitHub91> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/0VaHeA
<GitHub91> [milkymist-ng/master] asmicon/multiplexer: fix read tag delay - Sebastien Bourdeauducq
<wpwrak> guyzmo: code complexity is a bit of an issue indeed. and debugging is also unnecessarily hard at the moment. e.g., you can't trace most variable values and tracing those you can is inconvenient.
<wpwrak> guyzmo: did you show the M1 with MIDI ? or did you use it just as a non-interactive effect generator ?
<guyzmo> wpwrak - I did not have a controller, neither did the vision-r guys could give me one
<guyzmo> but that was not an issue
<guyzmo> people understood very well how a controller could interact
<guyzmo> either to switch the effects, or to modify an effect behaviour
<wpwrak> hmm. seeing is believing, though :)
<wpwrak> when showing the M1 to friends, the reaction i get is a polite "nice geek gadget. pretty colors." (with a stifled yawn) when i show it just generating things, to "THIS IS SO COOL !" when i just run one patch but with MIDI control
<wpwrak> i can't imagine that it wouldn;t have a similar effect on more experienced users, too. also, with MIDI, you start to care a bit more about latency :)
<guyzmo> wpwrak - well, I had the camera on
<guyzmo> so the "WHOA ! it's fast" effect was there
<guyzmo> so every time I say something is fast on the MM1, they just then believed me :)
<lekernel> writes work :)
<lekernel> we got DRAM
<lekernel> wpwrak: with the next UI, there shouldn't be any way to run it without controllers ;)
<lekernel> hmm... should we maintain any current SoC support in Linux?
<lekernel> or just switch everything to -ng
elldekaa has quit [Ping timeout: 240 seconds]
<Fallenou> yes !!!
<Fallenou> awesome !
<lekernel> I wouldn't be surprised if there were a couple of subtle bugs lurking in the darkness though
<Fallenou> lekernel: I pushed a few commits about exception handling, and I added if (rst_i) in always blocks
<Fallenou> I will do more intensive testing soon
cladamw has joined #milkymist
<Fallenou> to check if exception handling is robust
Jia has joined #milkymist
<lekernel> or not-so-subtle, eg accesses above 4MB do not work
<Fallenou> ^^
<lekernel> I suspect this is when crossing a bank boundary ...
elldekaa has joined #milkymist
<Hodapp> it warms my heart that people still exist who care about memory amounts that are less than 4 MB.
<Fallenou> ahah
<Hodapp> First programming class in undergrad, I heard plenty of "Why should I care about that? Computers have gigs and gigs of memory."
<lekernel> this is only true for computers that use DRAM...
<Hodapp> First engineering job, I was writing for a Cypress PSoC that had RAM measured in kilobytes
<lekernel> yes :)
<lekernel> SRAM is extremely expensive
<wpwrak> Hodapp: my first "home computer" had 1 kB in total. including screen memory :)
<Hodapp> wpwrak: I'm just going to halt this discussion immediately with: http://www.youtube.com/watch?v=Xe1a1wHxTyo
<wpwrak> when your program got too big, you had to sacrifice screen space ..
<Hodapp> Oh, you had a screen? We used to DREAM of having a screen!
<Hodapp> lekernel: This is all a bit foreign to me, but I do vaguely recall that DRAM has more complex refresh and access patterns... right?
<lekernel> among other complexities, yes
<Hodapp> I've not written enough stuff at this level... I need to.
<lekernel> essentially, writing a good performance controller for a modern DRAM (>= DDR) will likely make you a FPGA/computer architecture expert
<Hodapp> Hmmmmmm
<wpwrak> Hodapp: good one ;-)
<Hodapp> wpwrak: what, the Monty Python?
<wpwrak> aye
<Hodapp> it's one of my favorites
elldekaa has quit [Ping timeout: 244 seconds]
<wpwrak> i like the series that goes something like this: when i was a kid, we had to walk 10 km to school each day. through 2 m of snow. barefoot. ... and so on ... uphill. both ways.
elldekaa has joined #milkymist
TachyonDev has joined #milkymist
<Hodapp> there's a Slashdot thread that goes on for like 20 replies like that
cladamw has quit [Quit: Ex-Chat]
<GitHub49> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/milkymist/migen/commit/0bea1e25890908630f3cd403b0e41d4ecec042a1
<GitHub49> [migen/master] asmi: dat_wm high to disable data write - Sebastien Bourdeauducq
<lekernel> ah. that was a cache layout problem. now the CPU can access the whole 128M ...
<GitHub102> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/milkymist/migen/commit/68cd445662c8d015ff4ec9a65e8e68e3427d366d
<GitHub102> [migen/master] bus/wishbone2asmi: fix cache tag size - Sebastien Bourdeauducq
wolfspra1l has quit [Quit: leaving]
wolfspraul has joined #milkymist
<lekernel> elldekaa: when are you switching to migen? :)
Jia has quit [Quit: Konversation terminated!]
elldekaa has quit [Ping timeout: 245 seconds]
elldekaa has joined #milkymist
<lekernel> elldekaa: when are you switching to migen? :)
<elldekaa> hehe
<elldekaa> I cannot, it's to low level for me
<elldekaa> :p
<elldekaa> But I have to try it
<lekernel> elldekaa: sounds like a sensible HDL back-end for ORCC
<elldekaa> yep, probably something to try
<elldekaa> it should not be to hard
<lekernel> and you'll get features for free like actors accessing DRAM buffers at 10GBps off a $40 spartan-6
<Fallenou> :)
<elldekaa> with dma ?
<lekernel> yes
<elldekaa> sounds interresting, i need something like that for my TTA backend
<elldekaa> for the buffer of the motion compensation of the video decoder
<lekernel> and we'll get a video decoder, which is also something we need. so... :)
<elldekaa> several video decoders ;-)
<lekernel> well, after eliminating the patented and broken ones, I wonder how many will be left
<Fallenou> rm -rf h264 mpeg*
<elldekaa> alive : AVC / MPEG4-SP / AVS ... unpatented: i don't know (probably nothing)
<elldekaa> ^^
<lekernel> google webm?
<elldekaa> nop
<elldekaa> i don't know about the patent status of AVS
<elldekaa> your dma is cross-platform or not ?
<lekernel> not yet, we don't have a good memory access abstraction in the dataflow system atm
<lekernel> but it should
<lekernel> there are tons of things that are still missing in DF now :)
voidcoder has quit [Remote host closed the connection]
voidcoder has joined #milkymist
<elldekaa> lekernel: I need a chapter four with more details :D
* kristianpaul want to swich to llhdl ;D
TachyonDev has quit [Read error: Connection reset by peer]
TachyonDev has joined #milkymist
<lekernel> kristianpaul: llhdl and other bitstream hacks are too far away from the big M1 problem for me to be motivated to touch them atm
<kristianpaul> oh sure M1 as product has its own history
<lekernel> use your magic wand and make milkymist beat rpi on google trends, then I'll have time for llhdl
<kristianpaul> that will not happen, not us or anytime soon
<lekernel> then same for llhdl.
<kristianpaul> lol at leasy your port FN to rpi
<kristianpaul> s/leasy/least
<lekernel> this is one of the mindsets I want to avoid. and llhdl will do nothing towards this goal.
<lekernel> see Jon's email about the FN iPad application...
voidcoder has quit [Read error: Connection reset by peer]
voidcoder has joined #milkymist
lekernel has quit [*.net *.split]
lekernel has joined #milkymist
<kristianpaul> lekernel: i think we agree our goals may differ
<kristianpaul> lekernel: yup :)
<kristianpaul> (Jon's email)^
<kristianpaul> so why you started llhdl? what was your motivation at that time?
<kristianpaul> a weeked hack fpg internal project? ;-)
Gurty` has joined #milkymist
Gurty has quit [Ping timeout: 265 seconds]
<lekernel> that was january-march 2011, we had just started selling the rc2 boards, and I was still young and innocent at that time
<elldekaa> haha
<lekernel> then drawerware, unpopularity, etc. started to gradually piss me off
<elldekaa> I tried to advertise on the Milkymist One to one of my friend, researcher in 'new media art'
<elldekaa> he seems interested
<elldekaa> And I'm thinking about buying one for me :-)
<elldekaa> could be a good motivation for the migen backend
<elldekaa> =))
<kristianpaul> i must said i bought a M1 because the first llhdl example worked on it :)
elldekaa has quit [Remote host closed the connection]
voidcoder has quit [Remote host closed the connection]
togi_ has quit [Ping timeout: 272 seconds]
voidcoder has joined #milkymist
rejon has joined #milkymist
<lekernel> mwalle: what's the latest on the fast UART? how fast did you get it to work?
togi has joined #milkymist
togi has quit [Ping timeout: 240 seconds]
togi has joined #milkymist
<GitHub140> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/72ovIQ
<GitHub140> [milkymist-ng/master] bios: automatically enable hardware memory controller and test memory - Sebastien Bourdeauducq
rejon has quit [Ping timeout: 255 seconds]
elldekaa has joined #milkymist
lekernel_ has joined #milkymist
lekernel has quit [Ping timeout: 272 seconds]
wolfspra1l has joined #milkymist
wolfspraul has quit [Ping timeout: 260 seconds]
wolfspraul has joined #milkymist
elldekaa has quit [Ping timeout: 252 seconds]
wolfspra1l has quit [Ping timeout: 260 seconds]
lekernel_ is now known as lekernel
wolfspra1l has joined #milkymist
wolfspraul has quit [Read error: Connection reset by peer]
elldekaa has joined #milkymist
wolfspra1l has quit [Ping timeout: 245 seconds]
wolfspraul has joined #milkymist
wolfspraul has quit [Ping timeout: 272 seconds]
wolfspraul has joined #milkymist
sh4rm4 has quit [Remote host closed the connection]
sh4rm4 has joined #milkymist
sh4rm4 has quit [Ping timeout: 276 seconds]
sh4rm4 has joined #milkymist
voidcoder has quit [Read error: Connection reset by peer]
voidcoder has joined #milkymist
TachyonDev has quit [Read error: Connection reset by peer]