There plenty of us not working at Apple who can reuse the same approach for M5 and next generations of hardware.
I just think one good part of Marcan's work is that they streamed a lot of their workflow with all kind of problems occured along the way and you could see how to solve them.
And please so not let anti-llm crowd discourage you. People like me who want to use good hardware and already choose to pay for Apple one just need drivers that work good and feature complete - code purity and "quality" is secondary.
https://codyho.dev/blog/hypervisor-macbook-neo/
tl;dr you reboot the device with `macvdmtool`, you install m1n1 as the boot object, you talk to the m1n1 proxy over a python shell. I'm documenting the process as I go also (see: the blog posts, also my github repos) both so others can do it and as record of the clean room nature, but this really is just GPT go brrrrr
I guess its a good reason to try it with M6 mac mini or Vision Pro then (yeah I know AVP has locked bootloader). Thanks.
- boot macos under hypervisor (detailed guide in my part 1) into single user mode
- write your own metal program and run it as early in boot as you can
- trace all relevant graphics regions
- once you see the first kick, intercept that kick, then capture the full uat state
- reboot the device, then copy that whole uat state back into the machine, every bit exactly where it was
- perform the kick, verify the output page changes as expected
- have the LLM build all the objects itself in python
- repeat with different metal programs until we have all the behavior you want
- for a list of all behaviors you want, just look at the m1/m2 kernel driver and make sure everything they do has an analogue in your codebase
- if there's every any problems, there's a very simple debugging loop: 1. MAKE SURE YOU HAVE A REPLAYABLE CAPTURE. if you don't then priority #1 is to get that capture. once you have that capture, it's only a matter of time until it works