ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ahihi has quit [Ping timeout: 255 seconds]
ahihi has joined ##yamahasynths
andlabs has joined ##yamahasynths
andlabs has quit [Ping timeout: 246 seconds]
andlabs has joined ##yamahasynths
l_oliveira has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
SceneCAT has quit [Read error: Connection reset by peer]
SceneCAT has joined ##yamahasynths
futarisIRCcloud has joined ##yamahasynths
Ultrasauce has quit [Quit: Ultrasauce]
Ultrasauce has joined ##yamahasynths
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
andlabs has quit [Quit: Textual IRC Client: www.textualapp.com]
andlabs has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<cr1901> I was gonna try remote vectorizing today, but I don't think xpra does well w/ it lmao
<cr1901> And this laptop I have w/ me isn't powerful enough to open the entire die file
<ej5> what are you doing the vectorizing with?
andlabs has joined ##yamahasynths
<Lord_Nightmare> the spritesmind 68k thread, nemesis developed another vectorization/tracing helper tool
<cr1901> ? I use inkscape
<cr1901> anyways will this new tool become vaporware like exodus?
andlabs has quit [Ping timeout: 252 seconds]
<cr1901> err abandonware*
<Sarayan> LN: it's a visualization/annotation tool, not a tracing one
<cr1901> Sarayan: And well, isn't, strictly speaking, 68k fully RE'd b/c you and kevtris worked together?
<cr1901> recently*
<Sarayan> yeah, kevtris prefers if it's not too talked about
<Sarayan> but I guess it was for before the NT announce
<cr1901> mmm
andlabs has joined ##yamahasynths
ej5 has quit [Read error: Connection reset by peer]
<Lord_Nightmare> wondering how much more comple the 68010 is vs 68000
<Lord_Nightmare> x
<fseidel> not much
<fseidel> there's a small prefetch buffer which allows the CPU to execute small loops faster
<fseidel> you get 2 slots, so if one instruction is your loop body and the other is a DBRx instruction, you don't have to keep spending bus cycles to fetch those ops
<fseidel> there's also a few more states in the microcode to push the state needed to resume from a bus fault
<fseidel> that's basically it
<fseidel> that first feature is what Motorola call "loop mode" in the docs, which is a stupid name for what it really is, because it's not really a new mode
<fseidel> also, the microcode was edited to make MOVE SR, x trap in usermode
<Lord_Nightmare> does the 68k itself have a prefetch buffer of some sort, just the 68010 actually took real advantage of it?
<Lord_Nightmare> or was it an entirely new addition?
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<fseidel> this was a new addition
<fseidel> the original 68K effectively has a prefetch queue of length 1
<fseidel> by adding a second slot, you can now use it for more than just a primitive form of pipelining
<fseidel> ah, it looks like the 010 still only has 1 instruction of prefetch queue
<fseidel> which I guess makes sense since for "loop mode" you have one instruction currently being executed, and another one being prefetched
<fseidel> so yeah, they just made better use of hardware that was already there