[CDG5] MemRetry's objective

[Daniel B-J]

I would like quite a few things.

- An instance of the NK API written in C, so it is easy to understand and virtualize. Coherent documentation for just about everything would be nice.
- ease of porting to other systems, both real and virtual. Maybe an extension of MixedMode to another architecture?
- A "use OF" mode, which keeps OF running and makes a thin layer of virtualization around everything. Make device accesses OF driver calls?
- The ability to recursively virtualize itself. Want to test something crazy? Boot an instance of 9.2.4 inside of 9.2.4
- An instance of Linux running alongside 9 in a protected mem region(with 9 in control of course. Classic in reverse). Want to use Github? Interface via MPW or something.
- Ability to use FireWire DMA to debug connected systems (there is a primitive version of this out there, but it apparently needs support from the target computer).
- Ease of writing proper applications. Currently rather hard.

> On Apr 1, 2019, at 10:15 PM, Elliot Nunn <elliotnunn at fastmail.com> wrote:
> 
> I sympathise with both the perfect-emulation and the runtime-environment
> approaches. Sometimes I muse about what my own "Platonically ideal"
> MacOS would look like. These are some thoughts...
> 
> - built from source
> - runs on any CHRP machine
> - no requirement for a disk-based disk driver (yuck)
> - much of the "crud" in the System file factored out as extensions
> - a good API to make trusted calls out of the emulation layer
> - able to take advantage of a theoretical dual 68k/PowerPC emulator
>  runtime
> 
> Who's next?
> 
>> On 2 Apr 2019, at 8:13 am, Daniel B-J <danielbj314 at verizon.net> wrote:
>> 
>>> Currently it doesn't because MAME's emulation is still incomplete. Two years ago, I sent them several patches fixing CPU emulation so their model of a PowerMac 6100 almost reaches the gray screen. A hardware emulation issue related to CUDA/NVRAM is currently preventing it from booting - it seems that external interrupts won't be routed as expected. That causes the Netboot driver to hang forever. I think I'll be actually able to fix it...
>> 
>> I wonder how much work it would be to fill in custom ProductInfo tables instead of perfectly emulating lots of hardware. Interrupts get set up however you want (ProductInfo specifies code to handle them) and io can be done with fake NuBus cards. Device Tree nodes with custom drivers can be provided if some code insists on them.
>> 
>> Much of the craziness can probably be bypassed if everything is virtual anyways.
>> _______________________________________________
>> cdg5 mailing list
>> cdg5 at ucc.asn.au
>> https://lists.ucc.gu.uwa.edu.au/mailman/listinfo/cdg5
> 
> _______________________________________________
> cdg5 mailing list
> cdg5 at ucc.asn.au
> https://lists.ucc.gu.uwa.edu.au/mailman/listinfo/cdg5