View Single Post
  #10  
Old 6th May 2013, 04:38 AM
twostars twostars is offline
Junior Member
 
Join Date: Nov 2008
Posts: 8
Default

Not sure what happened to my post, but again -- thanks a lot for taking the time to help me understand what it's doing.

Regarding SEH, again, it seems libseh is what Wine uses (I won't link it again, in case that's why my post was removed).

Regarding memory management: so really all that comes down to is trying to conserve both unnecessary memory allocations (instead of allocating the entire thing, when you only need parts of it), and consequently CPU usage by not having to check where to write, each and every time.

Which of those sections aren't of concern to these reads/writes? Or the better question is, which of these special sections do we care about handling?

Apologies for all the questions, I really can't see anything else that explains the N64 in all that much detail (edit: that was kind of a silly thing to say, reading over the CPU's technical docs at the moment -- and well, there's source out there.). If you know of something, though, I'd happily wade through it instead of bothering you! Really appreciate your time.

Edit 2:
Hey, my post reappeared. I deleted it now anyway because I repeated it.
I came across this which pretty much answers my questions: http://infrid.com/rcp64/docfiles/n64maps.txt

Thanks

Last edited by twostars; 6th May 2013 at 05:23 AM.
Reply With Quote