Re: [B2-devel] Macintosh memory information?

[Alexander v. G. <kal...@un...>]

All great stuff, definitely helps! :)

Thanks!
  -- Alex

On 18.07.2012 09:29, Frank Trampe wrote:
> There is stuff of interest in Inside Macintosh: PowerPC System Software 
> and Inside Macintosh: Memory. The former is
> available on-line but not the latter. This ( 
> http://www.mindfiresolutions.com/mindfire/Mac_Memory_Manager.pdf [7] )
> may have some of what you need.
>
> On Wed, Jul 18, 2012 at 8:49 AM, Frank Trampe <fra...@gm... [8]> 
> wrote:
>
>> I think that you need the PowerPC edition/addition of Inside Macintosh. I 
>> will try to check on this in a few hours.
>> I believe that there is a copy available on-line somewhere, but I can 
>> scan the pages that you need if not.
>>
>> On Wed, Jul 18, 2012 at 7:21 AM, Alexander von Gluck 
>> <kal...@un... [6]> wrote:
>>
>>> Does anyone have any documentation on the memory layout of the old world
>>> Macintosh? (Performa 6400 era)
>>>
>>> I've been looking to rework how SheepShear manages memory and it's not
>>> completely clear to me how it does
>>> it's memory translation.  Most of the bugs I've seen on x86_64 are due 
>>> to
>>> the exact memory mapping on emulated
>>> powerpc systems (eg, hard coded memory addresses we *have* to map for 
>>> things
>>> to function) and something getting mangled
>>> on x86_64.
>>> https://github.com/kallisti5/sheepshear/issues/15#issuecomment-7045089 
>>> [1]
>>>
>>> I see memory maps for the really early Mac's, but am failing to find
>>> anything for the later old world machines
>>> online or in the old Macintosh service manuals.
>>>
>>> Here is what I know for a fact looking at the code:
>>>
>>> Low memory area, - 0x0        - 0x3000  (static 1:1 host:guest location)
>>> RAM,               0x0        - (memory size selected less then 1GB)
>>> ROM,               0x40800000 - 0x40C00000 (4MB mac rom)  (static 1:1
>>> host:guest location)
>>>
>>> Real addressing == "normal" allocation where memory locations are 
>>> dynamic,
>>> and we translate addresses to match
>>> Direct addressing == memory is directly addressed, mostly used on native
>>> PowerPC?
>>> Nat_mem offset == ???, guessing it's for native PowerPC
>>>
>>> It looks given the code below that the Macintosh has to be patched to 
>>> use
>>> the host memory
>>> addresses vs the emulator doing the memory translation (SheepShear 
>>> acting as
>>> a mmu to the guest)
>>> 
>>> https://github.com/kallisti5/sheepshear/blob/master/src/kpx_cpu/src/cpu/vm.hpp#L185 
>>> [2]
>>>
>>> The reason I ask here is because these changes could be pulled upstream 
>>> to
>>> SheepShaver.
>>>
>>>   -- Thanks!
>>>     Alex
>>>
>>> 
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. 
>>> Discussions
>>> will include endpoint security, mobile security and the latest in 
>>> malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ [3]
>>> _______________________________________________
>>> basilisk-devel mailing list
>>> bas...@li... [4]
>>> https://lists.sourceforge.net/lists/listinfo/basilisk-devel [5]
>
>
>
> Links:
> ------
> [1] https://github.com/kallisti5/sheepshear/issues/15#issuecomment-7045089
> [2] 
> https://github.com/kallisti5/sheepshear/blob/master/src/kpx_cpu/src/cpu/vm.hpp#L185
> [3] http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> [4] mailto:bas...@li...
> [5] https://lists.sourceforge.net/lists/listinfo/basilisk-devel
> [6] mailto:kal...@un...
> [7] http://www.mindfiresolutions.com/mindfire/Mac_Memory_Manager.pdf
> [8] mailto:fra...@gm...