<whitequark>
you know what preforked Apache is, right?
<whitequark>
this is called "unicorn" in Ruby/Rails world by some reason (mainly the weird sense of humor of the author)
<whitequark>
somehow rubyists often think that stupid names like "libpng" are too boring
<whitequark>
and they call libxml "Nokogiri"
<whitequark>
(that's a libxml binding, not a clone of course.)
<whitequark>
actually, nokogiri means "saw" in Japanese (the metal thingy, that is), but good luck determining the function of the package from its name.
<whitequark>
personally, I prefer these kinds of names by two reasons: 1) easier to google 2) similar things don't get called by similar names, and hence there is less confusion.
antgreen has joined #milkymist
<whitequark>
a preforked server for slow clients is called "Rainbows!". yes, exactly like that, with the bang symbol at the end.
cladamw has joined #milkymist
wolfspraul has joined #milkymist
cladamwa has joined #milkymist
xiangfu has joined #milkymist
xiangfu has joined #milkymist
xiangfu has joined #milkymist
qwebirc47389 has joined #milkymist
rejon has joined #milkymist
rejon_ has joined #milkymist
<kristianpaul>
xiangfu: thanks i'll try out
<xiangfu>
kristianpaul, nope :)
rejon_ has joined #milkymist
<cladamwa>
seems using tiny voltages changed between ground contact and cable shield is worth paying attention to capture action of insertion/removal but probably not in M1 case. With this tech, it should be more applied in measurement industries.
<GitHub64>
[flickernoise] wpwrak pushed 1 new commit to imaginarium: http://git.io/mZARug
<GitHub64>
[flickernoise/imaginarium] images: make images array variable - Werner Almesberger
<wolfspraul>
wpwrak: what happened?
<wpwrak>
seems that one of the building's infrastructure power lines failed. elevators were down, too.
xiangfu has joined #milkymist
<wolfspraul>
oh
<wolfspraul>
so you had to climb 13 floors?
<wpwrak>
naw. i didn't run out of any urgent supplies :)
<wolfspraul>
ah good :-)
<wolfspraul>
you were worried that my pcb core idea would fail over expensive copper, so I checked
<wpwrak>
i just checked the elevators to know the general status of the infrastructure. to ask the janitor, i would have had to climb those 14 floors ...
<wpwrak>
and ?
<wolfspraul>
price of a 50x60cm core is 5-11 USD depending on thickness
<wolfspraul>
roughly
<wolfspraul>
say 5 USD for a 0.3mm core, then 11 USD for 3mm
<wpwrak>
and the same in 3 mm acrylic ?
<wolfspraul>
copper makes no big difference at all, so the range is still 5-11 USD
<wpwrak>
ah, interesting
<wolfspraul>
one by one. pcb makers don't know much about acrylic :-)
<wpwrak>
so they throw in all the chemistry "for free"
<wolfspraul>
there must be a difference, of course. but I would only be able to find it out if I negotiated hard prices for larger volumes, which is too tiring just for the heck of it.
<wolfspraul>
say for 1000 50x60 panels - I'm sure there will be a difference whether I want copper or not, and how thick the copper is, etc.
<wolfspraul>
but if I just buy 1, it's the same 10-11 USD for 2.5mm or 3mm, with or without copper
<wolfspraul>
just fyi
<wolfspraul>
my feeling is that the copper part must be < 1 USD (of those 11)
<wpwrak>
not a bad price. at one of the local shops, the same amount of acrylic (unprocessed) would be around USD 18
<wpwrak>
lekernel: i'm looking for a place to put things like the pacman, the heavily midified tornado, etc. these are code examples that illustrate how things work but they may not be readily usable like the rest of the patches
<wpwrak>
lekernel: i'd still like to keep them in flickernoise.git, to keep them synchronized with the rest.
<wpwrak>
lekernel: what i wouldn't want to happen is that they end up in a web update by accident
<wpwrak>
lekernel: would (a) subdirector(y|ies) in patches/ be safe ?
<lekernel>
yeah, the webupdate patches are handpicked atm anyway
<wpwrak>
oh, perfect :) thanks !
<wpwrak>
it seems to be surprisingly difficult to get the frame number wrap around the maximum. somewhere, there's something very weird going on ...
<wpwrak>
(and no, i'm not using % ;-)
antgreen has joined #milkymist
LmAt has joined #milkymist
wpwrak has joined #milkymist
sh4rm4 has joined #milkymist
<lekernel>
whoa! it synthesized!
<lekernel>
and without complaining dozens of times about unroutable clocks after 20 minutes of runtime at each attempt
cwoodall has joined #milkymist
kilae has joined #milkymist
<lekernel>
it even works (or at least, the 1x clock does and all the PLLs lock). great!
<GitHub14>
[migen/master] bus/dfi: filter signals by direction - Sebastien Bourdeauducq
<GitHub53>
[milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/nY3Jfg
<GitHub53>
[milkymist-ng/master] Generate all clocks for the DDR PHY - Sebastien Bourdeauducq
<kristianpaul>
good !, free IP cores seems to be usefull after all ;)
<Hodapp>
I hadn't realized Milkymist was semi-compatible with MilkDrop... maybe if I'd ever have used the latter or read the thesis paper it would have helped
<wpwrak>
Hodapp: we have a the option of using a nicer syntax, though
<wpwrak>
Hodapp: milkdrop syntax is kinda evil :)
<lekernel>
hmm... if I make all accesses to a single page of DRAM and keep that page open, I should not need to refresh, right?
<lekernel>
(of course, this will destroy the data in the other pages)
<lekernel>
I'm thinking about the simplest way to do the startup calibration of I/Os ...
<lekernel>
driving the DRAM pins directly from a software routine (like the initialization sequence is done) sounds interesting, but refreshes might complicate things a bit
<lekernel>
I guess it gives Verilog coders more job security
<Fallenou>
ahah
<Fallenou>
it made all the red signals of my simulation disappear
<Fallenou>
magic initialization
<Fallenou>
\o/
<Fallenou>
and mmu stores seem to work as well (at least in simulation)
lekernel_ has joined #milkymist
<larsc>
Fallenou: nice :)
<lekernel_>
are there any DDR1 memories with differential DQS?
<lekernel_>
that supposedly DDR1-compatible PHY has hardcoded differential buffers for DQS, but afaik all DDR1 memories have single ended DQS
<lekernel_>
[{#~#{! that crap won't also generate the correct number of serdes I/O buffers
<lekernel_>
I guess it is safe to assume it has never been tested with DDR1 and with a data width different from what is installed on NWL's devboard ...
<lekernel_>
ha! now, of course, those 'unroutable clock' errors that I mentioned earlier and friends are coming in