#
✕ nick:nickchan
#asahi-re · 2025-04-06 11:43
nickchanthere are like 4 ctrr regions that can be configure on m4
#asahi-re · 2025-04-06 11:41
nickchanit also has to because the core comes out of reset in EL2 with GL available but disabled
#asahi-re · 2025-04-06 11:40
nickchanit definitely happens inside sptm according to some tweets i have seen
#asahi-re · 2025-04-03 17:18
nickchanwhich I may do on a11 soontm
#asahi-re · 2025-04-03 17:16
nickchanlike, at that point i am not sure if proper hypervisor is worth it compared to just hijack xnu vbar handling and tracing by disabling access in pagetables (all under sptm)
#asahi-re · 2025-04-03 17:13
nickchanwhich is ultra complex, of course
#asahi-re · 2025-04-03 17:12
nickchansuppose that cannot be worked around without bugs the way I see is run m1n1 in EL2 under sptm in GL2 and then have (possibly NV if sptm & xnu really does not like it) GL1 sptm and EL1 xnu
#asahi-re · 2025-04-03 17:05
nickchanon 15.2
#asahi-re · 2025-04-03 17:05
nickchanright and after unwrapping the macOS kernel macho from the img4 try setting the macho as the custom boot object
#asahi-re · 2025-04-03 17:01
nickchanneed to disable ctrr too
#asahi-re · 2025-04-03 17:01
nickchanfrom the ipsw
#asahi-re · 2025-04-03 17:01
nickchanyuka: does setting the kernel for the ipsw as the custom boot object work at least
#asahi-re · 2025-03-05 05:52
nickchanchadmed: drm-misc
#asahi-re · 2025-03-05 05:50
nickchanregardless of compatibility it's dodgy
#asahi-re · 2025-03-05 05:50
nickchanchadmed: the dodgy thing is apple,txxxx-something followed by apple,hxx-something
#asahi-re · 2025-03-05 03:48
nickchan(hopefully soon drivers/perf/apple_m1_cpu_pmu.c can support down to a7 so that kind of source naming is not all that freaky)
#asahi-re · 2025-03-05 03:47
nickchanin itself, too
#asahi-re · 2025-03-05 03:47
nickchanBut using both "Hx" and "Txxxx" is dodgy
#asahi-re · 2025-03-05 03:46
nickchansource file names are just a bad idea because all that means is sharing a codebase
#asahi-re · 2025-03-05 03:34
nickchanchadmed: AppleH7DisplayPipe.cpp
#asahi-re · 2025-02-25 12:24
nickchan"write parts of the definition of cluster->apsc_pstate to the region just after the definitions"
#asahi-re · 2025-02-25 12:23
nickchan>nonsense:
#asahi-re · 2025-02-25 12:22
nickchanhttps://github.com/AsahiLinux/m1n1/blob/c49bc2c38e4ec9251ee23bc51ca3c46bda582b4a/src/cpufreq.c#L209 m1n1 deals with those registers here but it's nonsense according to my understanding but then again maybe things has changed between a11 and m1
#asahi-re · 2025-02-25 12:15
nickchanhowever, it probably is reading MaxDVMRWeight from those registers
#asahi-re · 2025-02-25 12:14
nickchanas configured and filled in by iBoot
#asahi-re · 2025-02-25 12:14
nickchan>just from the dt
#asahi-re · 2025-02-25 12:13
nickchanadt, because patching the adt changes the frequency displayed by the pmgr kext
#asahi-re · 2025-02-25 12:13
nickchanit's also my understanding that xnu do not deal with those register and the frequency information is just from the dt
#asahi-re · 2025-02-25 12:12
nickchanchadmed: Not sure I only know a few fields in those register
#asahi-re · 2025-02-25 12:12
nickchanxnu calls it "MaxDVMRWeight" https://mrcn.st/p/44xr8mcE
#asahi-re · 2025-02-25 12:11
nickchanthese registers also holds the amount of cores are allowed to be active in the cluster when that state is enter (boost state defs)
#asahi-re · 2025-02-25 12:09
nickchanbut state 1 and above should be fine
#asahi-re · 2025-02-25 12:09
nickchanwell state 0 doesn't work like that it's a special state
#asahi-re · 2025-02-25 12:09
nickchanyeah that
#asahi-re · 2025-02-25 12:07
nickchanit measures the frequency
#asahi-re · 2025-02-25 12:07
nickchanwith the cpu_pstate_latencies experiments
#asahi-re · 2025-02-25 12:07
nickchanI cranked up A9 to 2448 MHz and A11 to 2112 MHz Ecore 2376 MHz Pcore like that
#asahi-re · 2025-02-25 12:06
nickchanand see if the experiments/cpu_pstate_latencies.py has anything to say about it
#asahi-re · 2025-02-25 12:06
nickchana simple experiment is to try to, say, overwrite definition of state 3 with definition of state 4
#asahi-re · 2025-02-25 12:06
nickchanchadmed: it very much does on a7-a11, t2 (different offset and different stride size on some chips)
#asahi-re · 2025-02-25 12:05
nickchanthis supposedly holds definitions for each pstate in strides of 0x20, for state 0-15 on m1
#asahi-re · 2025-02-25 12:04
nickchanchaos_princess: for voltages and frequencies, on m1 have you experimented with the registers at cluster->base (in m1n1 cpufreq.c terms) + 0x70000 ?
#asahi-re · 2023-06-05 17:28
nickchanthough because on s8000 the dfu sequence is manual must be done so it would still be very annoying
#asahi-re · 2023-06-05 17:27
nickchan64 possibilities
#asahi-re · 2023-06-05 17:27
nickchanI mean possibilities
#asahi-re · 2023-06-05 17:26
nickchanwell I already know that the CPU start offset for s8000 is 0xd4000
#asahi-re · 2023-06-05 17:26
nickchanassuming it is 16384 bytes aligned - probably, there are only 16 possibilities from 0x0 to 0x100000
#asahi-re · 2023-06-02 12:48
nickchanwell this is going to get annoying for me because the S8000 did not have EL2. I am assuming that the start offsets for T8103 was from corellium, since m1n1 does not have an hypervisor back then
#asahi-re · 2023-06-02 11:46
nickchanDoes anyone know where the CPU start offsets in https://github.com/AsahiLinux/m1n1/blob/2c531aa7ae99deed787d77ba8b778da96e8d8a6a/src/smp.c#L13 are obtained? I am trying to obtain the CPU start offset of the S8000 SoC.