Topic for #milkymist is now Radical Tech Coalition :: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs
<fpgaminer> kristianpaul: Glad you got it working :) I didn't do the port with serial communication on it :P But yeah, I vaguely remember having to tweak the clock on that port
<kristianpaul> Btw how this thing of
<kristianpaul> argh
<kristianpaul> Btw how is the math related to the relation of hashes per second and megahertz
<kristianpaul> for example i set your minner loop log of 5 but lets said i can achieve 200Mhz clock
<kristianpaul> Will be the same if i got a loop log2 at 3 but 100Mhz clock?
<kristianpaul> same performance i mean
lekernel has joined #milkymist
<fpgaminer> loop_log2=0 will give 1 hash per cycle
<fpgaminer> loop_log2=1 will give 1 hash every two cycles
<fpgaminer> loop_log2=2 will give 1 hash every four cycles
<fpgaminer> etc
peterkirn has quit [#milkymist]
<kristianpaul> ah ok
<roh> fpgaminer: are you using a m1 to mine?
<kristianpaul> fpgaminer: had you ever used serial comunication with your minner core?
<kristianpaul> I would like to know if what i'm tryin here worked for someone else already :)
<wpwrak_> bah, where's the pioneering spirit in today's youth ?
<kristianpaul> i'm trying !!!
* kristianpaul already bringed the scope..
<kristianpaul> btw i havet xst asumes GNS a when a non defined wire is assigned to a instanciate module :-|
<kristianpaul> doest work i doest work as i would expect.. one of two i need to confirm ;)
<wpwrak_> i already realized that it's mandatory to study the logs very carefully. xst won't just stop and tell you if something bad happens.
<kristianpaul> indeed
<kristianpaul> at least until the point you know what belons to what :)
DJTachyon has joined #milkymist
<fpgaminer> kristianpaul: I haven't personally used serial comms with my mining core, but I know other people have.
azonenberg has joined #milkymist
rejon has joined #milkymist
rejon has joined #milkymist
rejon has joined #milkymist
wolfspraul has joined #milkymist
rejon has joined #milkymist
rejon has joined #milkymist
wolfspraul has joined #milkymist
rejon has joined #milkymist
rejon has joined #milkymist
<GitHub72> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/milkymist/migen/commit/e62ac1d3a1a2855ed241ac9f29d9103afdc0d2a0
<GitHub72> [migen/master] corelogic/misc: contiguous split - Sebastien Bourdeauducq
<lekernel> wpwrak_: what's the next step for MIDI? a preprocessor so you #include the device descriptions?
kilae has joined #milkymist
elldekaa has joined #milkymist
sh4rm4 has joined #milkymist
wolfspraul has joined #milkymist
<wpwrak_> hehe :)
<wpwrak_> naw, i think i'll split the database: one part goes into a separate file where only device descriptions are allowed, and maybe leave the option open to have declarations in a patch as well
<wpwrak_> what's more important now will be the ability to detect what's actually connected
<wpwrak_> and to associate events with the source
<lekernel> okay
<lekernel> shall we push out webupdate images as soon as this is done?
<lekernel> then for the next release (1) USB bugfixing (2) support for short movies
<wpwrak_> it'll still be a while. my plan for now it to finish the existing feature set (i have a few small changes and i'll also rename a few identifiers, e.g., split "range" for devices into "fader" and "pot"), document it, and then let people have a look at it.
<wpwrak_> then add multi-images, the other "major" language extension
<lekernel> can we release an update before image sequences?
<wpwrak_> image sequences should take only a little time. probably less than a day
<lekernel> maybe, but release soon, release often
<lekernel> MIDI-USB is hot
<wpwrak_> sure. we should make more use of daily build, too
<wpwrak_> hehe, true :)
<lekernel> how? have an option in the web update to install the daily build, with a "use at your own risk" warning?
<lekernel> and btw daily builds should have the last commit id in the version numbers
<wpwrak_> something like that. maybe just have the means to select from a list of install options. and that could include the daily builds. maybe just make the URL for a master list configurable.
<wpwrak_> yes, we should track versions at a lot more places. build of libs, rtems, fn, soc, bios
<lekernel> ok. further reasons to get that MIDI-USB enabled update out soon *g*
<lekernel> then better version tracking + daily build support + USB bugfix + image sequences in the next
<lekernel> and hopefully some RTEMS cleanup
<wpwrak_> image sequence would be next. then the language should be more or less complete. then it needs documenting :)
<lekernel> I'll submit the idea of adding the last git commit in their version string
<wpwrak_> linux ? ;-)
<wpwrak_> the ultimate rtems cleanup ;-)
<lekernel> atm all builds from HEAD have "4.10.99" which doesn't makes much sense
<lekernel> I think Linux will take ages
<lekernel> especially if we run into M1-crashing heisenbugs and performance issues, and we probably will
<wpwrak_> i'd be worried a bit about performance issues, yes
<wpwrak_> also the MMU may need some tuning before it works well
azonenberg has joined #milkymist
sh4rm4 has joined #milkymist
ChanServ has joined #milkymist
DJTachyon has joined #milkymist
elldekaa has joined #milkymist
kilae has joined #milkymist
sh4rm4 has joined #milkymist
elldekaa has joined #milkymist
<GitHub192> [migen] sbourdeauducq pushed 4 new commits to master: https://github.com/milkymist/migen/compare/e62ac1d...244bf17
<GitHub192> [migen/master] corelogic/record: add to_signal convenience function - Sebastien Bourdeauducq
<GitHub192> [migen/master] bus/asmibus: fix typo - Sebastien Bourdeauducq
<GitHub192> [migen/master] corelogic/misc/multimux: less confusing variable name - Sebastien Bourdeauducq
elldekaa has joined #milkymist
sh4rm4 has joined #milkymist
<kristianpaul> what about a mmu-less linux is that severe lacks mmu that it will break most of the software and drivers currently Flicker Noise need?
<Fallenou> on mmu-less linux like uclinux any program can crash another program (or the kernel) AFAIK
<Fallenou> since there is no memory protection
<Fallenou> => no segfault, you can write anywhere and crash everything
<Fallenou> it's really a problem if you want to have a stable system
<kristianpaul> yes i see now..
dvdk has joined #milkymist
<Fallenou> going to sleep, will get up early tomorrow to work on the mmu :) would be nice to make memory *stores* to work too !
<Fallenou> gn8 !
<kristianpaul> n8
<Fallenou> for those who want to have a look at the mmu project there is a ready-in-a-few-seconds simulation project here : https://github.com/fallen/milkymist-mmu-simulation
<Fallenou> if you already have ISE installed you can simulate the lm32-mmu in less than a minute
<Fallenou> will document this a little bit more tomorrow :)
<dvdk> Fallenou: just some 15minutes ago I googled for your code (and found it)
<dvdk> so nobody around who can share some insights on the MMU driver?
<dvdk> i'm just wondering what 'wcsr tlbvaddr,%0' refers to. tlbvaddr? that csr is not in the lm32 manual afaik
<dvdk> did you guys extend gnu as?
<kristianpaul> i remenber Fallenou modified toolchain
<dvdk> so unnccessary... just use hexcodes.
<dvdk> ok, cloning his git repo, and looking at the verilog code to see which new CSR numbers he's using
<dvdk> OMG, he's really done it: kristianpaul: do yo uknow e
<dvdk> uh, copy-paste reror