lekernel changed the topic of #milkymist to: Mixxeo, Migen, Milkymist-ng & other Milkymist projects :: Logs: http://en.qi-hardware.com/mmlogs :: Mixxeo preorder lists.milkymist.org/pipermail/devel-milkymist.org/2013-May/003344.html
<rjo> lekernel: sorry. that patch was supposed to have max(2, n)
<rjo> lekernel: i got my ones and twos wrong....
Scopeuk is now known as Scopeuk-AFK
kristianpaul has quit [Ping timeout: 264 seconds]
Scopeuk-AFK is now known as Scopeuk
Martoni has joined #milkymist
lekernel has joined #milkymist
<GitHub86> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/sR-elQ
<GitHub86> migen/master 6e11954 Robert Jordens: genlib/roundrobin: fix n==1 case (correctly)
_florent_ has joined #milkymist
<ysionneau> lekernel: about my email in moderation, do you want me to send it again with no attached files and with links instead? (the whole email was 200 kB instead of the 40 kB which is the max accepted)
<cde> shouldn't we increase that limit a bit
bhamilton has joined #milkymist
<lekernel> just moderated it
kristianpaul has joined #milkymist
bhamilton has left #milkymist [#milkymist]
lekernel has quit [Ping timeout: 248 seconds]
<ysionneau> thanks :)
<ysionneau> cde: 40 kB is a bit low indeed at least for PDF files :)
<cde> maybe it's a good thing. PDF is evil ;)
<cde> let's share .tex or .rst
<cde> btw https://code.google.com/p/wavedrom/ <= very nice for sharing waveforms
<ysionneau> cool :)
lekernel has joined #milkymist
<stekern> ysionneau: that was a nice and comprehensible documentation of the mmu, there's only one thing that I'm not sure about - the value written to TLBBADVADDR on an itlb miss
<stekern> in the document it sounds like it's not updated with the address that actually caused the miss, but whatever happens to be in execute stage
<stekern> is that right?
sb0 has joined #milkymist
<GitHub168> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/H5mP8g
<GitHub168> migen/master cec8fc4 Sebastien Bourdeauducq: fhdl/specials/Instance: fix item sorting
<ysionneau> 12:44 < stekern> ysionneau: that was a nice and comprehensible documentation of the mmu < thanks :)
sb0 has quit [Quit: Leaving]
<ysionneau> hum reading the paragraph again I'm not sure it's correct
<ysionneau> stekern: I will look closer at this paragraph tonight I think :)
<ysionneau> thanks for the feedback!
_florent_ has quit [Ping timeout: 250 seconds]
bhamilton has joined #milkymist
bhamilton has left #milkymist [#milkymist]
<stekern> ysionneau: my pleasure
<ysionneau> I think mwalle already told me about this paragraph, I thought I had address this issue
<ysionneau> it seems not
<GitHub161> [mibuild] sbourdeauducq pushed 1 new commit to master: http://git.io/yM_miA
<GitHub161> mibuild/master f7f19b7 Sebastien Bourdeauducq: Fragment -> _Fragment
<stekern> I know how it is. When you looked too long at your own documentation, errors start becoming hard to find =P
<stekern> I'm curious though, how does the exceptions work in lm32. I guess for exceptions that happen in < execute stage, they are just propagated into execute and then taken
<stekern> but are all mem stage (apart from mmu) exceptions just address related?
<stekern> (i.e. any external bus errors can't be captured?)
<ysionneau> 15:27 < stekern> I'm curious though, how does the exceptions work in lm32. I guess for exceptions that happen in < execute stage, they are just propagated into execute and then taken < yes, when the exception is raised, it is really triggered once the instruction is in the X stage
<ysionneau> documentation says that bus error exception are more or less non deterministic :)
<ysionneau> I think that there is no easy way to raise an exception after the execute stage in the lm32 pipeline
<stekern> ok, yes, that makes sense
<stekern> and I think I recall that you had to induce a 1 cycle delay for the dtlb miss exception just because of this, right?
<ysionneau> indeed
<ysionneau> so that the instruction (load or store) is still in the X stage
<ysionneau> stekern: after checking in the code, the sentence in the documentation is correct
<stekern> I wonder though, does execute stage have any sideeffects that wouldn't be cleared by the dtlb miss exceptions? (if it would be taken in mem stage I mean)
<stekern> (as a comparison, in mor1kx we take all exceptions in mem stage)
<stekern> hmm, yes, but hasn't the itlb miss pc moved up to execute stage when that happens?
<stekern> or is the 'itlb_exception' signal connected straight from the mmu?
<ysionneau> it's connected straight from the mmu
<GitHub164> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/3bP_Ug
<GitHub164> migen/master 9c7ad6b Sebastien Bourdeauducq: fhdl: RenameClockDomains decorator
<GitHub56> [milkymist-ng] sbourdeauducq pushed 1 new commit to master: http://git.io/eHExVQ
<GitHub56> milkymist-ng/master bf32559 Sebastien Bourdeauducq: Use RenameClockDomains decorator instead of add_submodule
<ysionneau> oh you're right
<ysionneau> itlb_miss_x comes from the itlb module but it's "buffered" from the miss_f
<ysionneau> miss_x <= miss_d; and miss_d <= miss_f;
<ysionneau> so itlb_exception is raised only when the instruction is in the X stage :)
<ysionneau> so pc_x should be, in theory, the address of the instruction whose fetch caused the exception
<ysionneau> so I should fix the documentation :)
<ysionneau> I should have paid attention to the "_x" suffix =)
<stekern> ah, I didn't even look further up in the file, I just assumed it "has to be" the case =P
<GitHub132> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/QHjYHw
<GitHub132> migen/master 61b8958 Nina Engelhardt: fix synthesis translate on/off switch
mumptai has joined #milkymist
Martoni has quit [Quit: ChatZilla 0.9.90.1 [Iceweasel 17.0.7/20130626001350]]
azonenberg has quit [Read error: Connection reset by peer]
azonenberg has joined #milkymist
lekernel has quit [Quit: Leaving]
bhamilton has joined #milkymist
bhamilton has left #milkymist [#milkymist]
Alarm has joined #milkymist
Alarm has quit [Quit: ChatZilla 0.9.90.1 [Firefox 22.0/20130618035212]]
Scopeuk is now known as Scopeuk-AFK