#asahi-dev · 2023-10-26 17:49
czathanks for the link!#asahi-dev · 2023-10-26 17:49
czai should give that a go, it probably can get windows way further than i'll ever do on my own, especially with no knowledge about the platform :p#asahi-dev · 2023-10-26 17:49
czai see, someone had that idea before me, not surprised#asahi-dev · 2023-10-26 17:48
czathough the bootloader was light work compared to this, some minor memory related stuff + weird framebuffer format#asahi-dev · 2023-10-26 17:47
czai worked on porting a bootloader to m1 a few days ago and now i wanted to see how far windows can get#asahi-dev · 2023-10-26 17:46
czathe thing im trying to run under m1n1? yep lol#asahi-dev · 2023-10-26 17:45
czaill give that a go now that my code is actually being run :^)#asahi-dev · 2023-10-26 17:45
czayep that's exactly what it says after it reconnects to the proxy, thank you for that!#asahi-dev · 2023-10-26 17:43
czai'll give that a go, thanks!#asahi-dev · 2023-10-26 17:42
czai knew i was doing something wrong because none of my changes were actually there#asahi-dev · 2023-10-26 17:42
czaah, that makes a lot more sense#asahi-dev · 2023-10-26 17:40
czawhich does not contain my changes#asahi-dev · 2023-10-26 17:40
czabecause if not, then any exceptions from the underlying os will be caught by stage 1 m1n1#asahi-dev · 2023-10-26 17:40
czaso now, can the chainloaded m1n1 that's running under the hypervisor run as a hypervisor itself?#asahi-dev · 2023-10-26 17:39
czait seems to me that when i use the run_guest.py script, whatever payload i provide is what is run under the hypervisor, is that correct?#asahi-dev · 2023-10-26 17:38
czaim using the run_guest.py script already, but i think im just misunderstanding the boot process#asahi-dev · 2023-10-26 17:36
czabut i want the newly built m1n1 to act as the hypervisor#asahi-dev · 2023-10-26 17:36
czasorry if i cant explain what im talking about#asahi-dev · 2023-10-26 17:36
czaalright, what im wondering about is after loading my new payload with newly built m1n1 and uboot how do i get this *whole thing* to run under the m1n1 i just chainloaded?#asahi-dev · 2023-10-26 17:34
czaso the proxy mode i get by using -v boot args comes from stage 1?#asahi-dev · 2023-10-26 17:33
czaor do i have to put it on the efi partition for stage 1 to chainload? that sounds like it will take a lot of time to test a single build#asahi-dev · 2023-10-26 17:32
czaso i can run the uefi os under the newly built hypervisor#asahi-dev · 2023-10-26 17:32
czais there an easy way to run the new build of m1n1 as the hypervisor?#asahi-dev · 2023-10-26 17:29
czaso i wanted to somehow work around that and return the value from one of these registers#asahi-dev · 2023-10-26 17:29
czayeah i figured that out, the esr was weird but there seems to be an apple PMU equivalent#asahi-dev · 2023-10-26 17:25
czahello, i was wondering if anyone could tell me what's the recommended way to hack on m1n1? im trying to add a few things to the hypervisor but im not sure what would be the fastest way to test out my changes. im looking into handling some missing system registers like PMCCNTR_EL0 (reading it gives me a sync abort), is there perhaps a way to handle that using the proxy? im not very well versed with aarch64 and apple platforms but i'm