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
cladamw has joined #milkymist
antgreen has joined #milkymist
Jia has joined #milkymist
xiangfu has joined #milkymist
dvdk has joined #milkymist
rejon has joined #milkymist
rejon has joined #milkymist
Jia has joined #milkymist
wolfspraul has joined #milkymist
cladamw has joined #milkymist
wolfspraul has joined #milkymist
wolfspraul has joined #milkymist
voidcoder has joined #milkymist
voidcoder has joined #milkymist
dvdk has joined #milkymist
wolfspraul has joined #milkymist
wolfspraul has joined #milkymist
xiangfu has joined #milkymist
robmyers has joined #milkymist
robmyers has joined #milkymist
cladamw has joined #milkymist
cladamw has joined #milkymist
cladamw has joined #milkymist
rejon has joined #milkymist
elldekaa has joined #milkymist
Martoni has joined #milkymist
rejon has joined #milkymist
fpgaminer has joined #milkymist
xiangfu has joined #milkymist
<cladamw> wpwrak, i'm considering let LINE_OUT connector to adjacent to LINE-IN con. together as U23 is within them which is not good for diagnosis.
isa has joined #milkymist
voidcoder has joined #milkymist
<isa> test
cladamw has joined #milkymist
cladamwa has joined #milkymist
cladamw has joined #milkymist
<wpwrak> cladamw: hmm, let's see ...
<wpwrak> commercially available dual 3.5 mm jacks have a center to center distance of 15 mm
<wpwrak> like we do in M1rc3
<wpwrak> adam really needs a permanent internet connection ...
<cladamwa> wpwrak, no, i have two laptops. ;-) In Windows I also installed an irc server, sorry
<cladamwa> wpwrak, i prefer to use current two con. rather than finding a dual 3.5 jack
<wpwrak> oh sure, two connectors is okay
<cladamwa> wpwrak, or place parts in bottom side( which is not I want ).
<wpwrak> i just looked for indications of what distances are used
<cladamwa> i see
<cladamwa> since the case should already being not same as rc3. so i planned to like this.
xiangfu has joined #milkymist
<wpwrak> if we consider that a user may want to connect 6.3 mm jacks, then at least about 15 mm center-to-center distance would be reasonable. a 6.3 mm jack has an outer diameter of about 13-14 mm
<wpwrak> (6.3 mm jacks) via adapters, of course
<cladamwa> hmm ... 6.3 mm jack seems a popular one for the musical instruments. I hope you are not serious on this, are you ?
<wpwrak> semi-serious :)
<wpwrak> i'm not entirely sure whether professional users would trust a 6.3 mm to 3.5 mm adapter
<wpwrak> but i've seen a fair bit of 6.3 mm in higher end equipment. so i can very well imagine that someone out want to connect to that
<wpwrak> and if the spacing is too tight, things get messy
<wpwrak> looking at dual 3.5 mm stereo connectors ... they look a bit scary. quite tall (24.0-26.7 mm) and probably need a screw for stress relief
<cladamwa> wpwrak, yes, when i went to a swimming poor which they play music by huge speakers with 6.3 mm pluger, their instruments can set a lot audio effects and equalizers.
<wpwrak> so that's probably not a viable alternative. both would have 15.0 mm center-to-center, though
<cladamwa> the rear of intruments are all 6.3mm receiptacles.
<cladamwa> wpwrak, yeah...the length can't be used in m1, too waste space.
<wpwrak> how about moving U23 under the expansion board ? between J21 and U1 ? there seems to be a bit of free space
<cladamwa> wpwrak, the expansion board can do such 6.3mm CD-in then use SPDIF-out. :-)
<wpwrak> ;-))
<cladamwa> sure, why not. :) but i was just considering to free space under expansion area. Since who knows will build great extra-value-added for m1 though expansion. I know like you are !
<wpwrak> i'm not so much worried about free space in general but about the maximum height of the things under the expansion board. it seems that U23 wouldn't make a difference in this regard
<cladamwa> so i meant if m1r4's case doesn't need to same as rc3 as dvi-i connector-variant there.
<cladamwa> oah...yeah. the U23's height is not too tall, so if you prefer to place there, then we go there. :-)
<wpwrak> yes, i'd rather have U23 under the expansion board than the two audio jacks very close to each other
<wpwrak> even without 6.3 mm adapters, it's not very convenient to have very closely spaced connectors
<wpwrak> (case) yeah. it'll be a new design. that much is certain :)
<wpwrak> unless xiangfu wants to try his disc-cutting drill ;-)
<wpwrak> that's the same as before ?
<cladamwa> updated. :-) alright, collecting feedbacks here: http://en.qi-hardware.com/wiki/Milkymist_One_R4_Layout_History
<cladamwa> sorry that they are in Chinese. :)
<wpwrak> yeah, the update looks good
<wpwrak> (cn) ;-)
<cladamwa> your internal usb (with atusb dongle) I'll add it.
<cladamwa> wpwrak, another question, where we supposedly place those un-used LEDs ?
<cladamwa> wpwrak, current TPs for LEDs-M are under bottom side. I'm thinking to place them to top side for easy. Is it okay to you ?
<wpwrak> i don't have a place for them. what could be a little interesting is to have a few of them on the pcb edge, below the eastern edge of the expansion board
antgreen has joined #milkymist
<wpwrak> that way, they could be used to signals things there, if someone wants that
<wpwrak> top side is fine with me
<cladamwa> still have 8 un-used LEDs, so few of them to the eastern edge of expansion board, or all ?
<wpwrak> your choice :)
<cladamwa> (LEDs TPs on top) okay. tks.
<cladamwa> phew...
<wpwrak> ah, and we can DNP the "reserved" LEDs anyway. i would place them in the prototype run, to check things, but then we can save wolfgang a few cents :)
<wpwrak> nice :)
<cladamwa> place them as the idea you gave, but we DNP them in m1r4.
<wpwrak> but there's not enough room for all of them. at least not if we design for side-facing leds, which have their long side parallel to the pcb's edge
<wpwrak> actually ... they may just fit :)
<wpwrak> the green area is 60 mm on my screen and you can probably have one LED every 8 mm, so that would work
<cladamwa> rough just for illustration for house, I'll tell them to centralize them. :-)
voidcoder has joined #milkymist
sh4rm4 has joined #milkymist
voidcoder has joined #milkymist
kilae has joined #milkymist
antgreen has joined #milkymist
azonenberg has joined #milkymist
elldekaa has joined #milkymist
voidcoder has joined #milkymist
mumptai has joined #milkymist
hypermodern has joined #milkymist
<GitHub185> [llvm-lm32] jpbonn pushed 1 new commit to master: http://git.io/c4y35w
<GitHub185> [llvm-lm32/master] Added note on building CompilerRT, corrected some PATHS in directions. - jpbonn
<[florian]> hey there
<[florian]> anyone seen sebastien recently?
<larsc> seen on IRC?
<wpwrak> i think he's traveling at the moment
<GitHub172> [llvm-lm32] jpbonn pushed 1 new commit to master: http://git.io/HHZCNw
<GitHub172> [llvm-lm32/master] Added note for OSX. - jpbonn
<Fallenou> nice link kristianpaul :)
<Fallenou> I finally got the MMU to work on the FPGA
<Fallenou> I mean, to pass the 15 test cases without crashing the soc :)
<Fallenou> Will commit very soon
<kristianpaul> Fallenou: oh !
<kristianpaul> great
<kristianpaul> what you did it to make it work=
<kristianpaul> s/=/?
<kristianpaul> sorry i havent read logs since sunday..
<Fallenou> I forgot to take into account some internal signaling of the pipeline
<Fallenou> I am not totally sure that it's working 100% correctly, I only tested 15 different load/store configurations
<Fallenou> I will add more tests with more instructions to stress test the pipeline a little bit
<Fallenou> I tested all the instructions sequences of store (nop)* load (nop)* with 6 instructions (the pipeline size)
<Fallenou> like store load nop nop nop nop , store nop load nop nop nop etc
voidcoder has joined #milkymist
<Fallenou> gn8 !
dvdk has joined #milkymist
sb0 has joined #milkymist
<sb0> hi
<wpwrak> hello traveling salesman ;-)
<kristianpaul> hello
<wolfspraul> Fallenou: wow congrats!
<wolfspraul> and safe travels Sebastien...
<wolfspraul> safe and happy :-)
voidcoder has joined #milkymist