#asahi-re · 2026-07-21 19:27
yuka> <chaos_princess> it is unlikely that you will succeed. the relevant bits are in iboot, and you can't change it#asahi-re · 2026-07-21 19:26
yukaas people have been telling you, we would all expect this stuff to be locked down in your device/setup#asahi-re · 2026-07-21 19:24
yukachainloading another m1n1 shouldn't affect privileges in any way, but I suspect you mean something else?#asahi-re · 2026-07-21 19:23
djthere isn’t any known limitations of chainload path having less privileges or is there#asahi-re · 2026-07-21 19:23
djthere isn’t any known limitations of chainload path having less privileges or is there#asahi-re · 2026-07-21 19:21
djokay I can’t write them in EL2#asahi-re · 2026-07-21 19:17
djtested a read on them, they came back unconfigured. let’s try it out#asahi-re · 2026-07-21 19:16
djwe shall find out today :) hope for the best. Just found something related to ACC-CTRR etc locks which sptm handles before xnu handoff that might be enabling CPM writes#asahi-re · 2026-07-21 19:12
sveni hope i'm not right :D#asahi-re · 2026-07-21 19:12
svenif it's bugged all we can do is file a feedback assistant report and hope for the best essentially :(#asahi-re · 2026-07-21 19:11
djsptm is seemingly doing some setup that m1n1 does not and that’s why we can’t start secondaries, that’s the current theory. If that doesn’t work, I’m out of ideas other than iboot being actually being bugged you may as well be right lol#asahi-re · 2026-07-21 19:10
djI meant the path from iboot to sptm or iboot to fuos. I was comparing t6050 specific paths so could’ve missed something#asahi-re · 2026-07-21 19:08
svenand the fuos path needs to somehow lock down all sysregs, etc.#asahi-re · 2026-07-21 19:08
sventhe paths must look very different, the regular macos one needs to load SPTM and XNU to memory#asahi-re · 2026-07-21 19:08
djregular macOS seems to get a flag smth along the lines of apple trusted#asahi-re · 2026-07-21 19:08
dji did look into iboot’s handoff and there wasn’t much diff in how it performs handoff to us or regular macos. there was some something about svc #2 and svc #3 which was t6050 specific#asahi-re · 2026-07-21 19:07
djit’s a possibility#asahi-re · 2026-07-21 19:05
svenand the fuos path is just not very well tested by apple#asahi-re · 2026-07-21 19:05
svenyes, because the boot path for fuos is different from the "regular" macos boot path#asahi-re · 2026-07-21 19:03
djmaybe it’s a layer up, in sptm#asahi-re · 2026-07-21 19:03
djtried countless things from xnu that is t6050 specific, like the symbol clearly says so, but it doesn’t work still#asahi-re · 2026-07-21 19:03
djgonna dig into sptm too#asahi-re · 2026-07-21 18:58
djlike a bug specific to fuos that doesn’t affect xnu?#asahi-re · 2026-07-21 18:13
sveni still suspect that the smp issue is just some bug in iboot :(#asahi-re · 2026-07-21 14:44
j`eydj: https://developer.arm.com/documentation/ddi0602/2022-06/Base-Instructions/STTR--Store-Register--unprivileged--#asahi-re · 2026-07-21 14:41
djis it possible to issue a store from el1 somehow#asahi-re · 2026-07-21 14:25
djeven after settings the pmp bits xnu does, still couldn’t write to CPM + 0x40f8. what sorcery is apple doing#asahi-re · 2026-07-21 14:08
djyes I’m keeping notes of it#asahi-re · 2026-07-21 14:07
yukadj: if you can figure out what the impact of the individual init things are (x makes y writable), having documentation of this would be amazing#asahi-re · 2026-07-21 14:07
djwriting to certain regions indeed seems blocked until you enable certain bits, and reversing xnu’s init is helping with exactly that but it’s a tedious process. once it works, I’ll try to narrow it down to exactly what was needed#asahi-re · 2026-07-21 14:05
djsven: yes I keep finding one init after another that is missing and explains the SError perfectly. lol still haven’t hit the wall#asahi-re · 2026-07-21 07:31
yukahttps://github.com/AsahiLinux/m1n1/pull/633#asahi-re · 2026-07-21 07:13
sventhat change is more that trivial enough ;)#asahi-re · 2026-07-21 07:13
svensure, go ahead#asahi-re · 2026-07-21 07:10
nickchanso there's precedent#asahi-re · 2026-07-21 07:10
nickchanthe controls to modify the cpu p-state definitions are disabled when the kernel boots on t8103 already#asahi-re · 2026-07-21 06:56
yukat8142 pcie reg layout looks close enough that it could#asahi-re · 2026-07-21 06:52
yukaI would also like someone to check if the same works for t8142#asahi-re · 2026-07-21 06:51
yukaSo I request permission to publish the code change for that directly#asahi-re · 2026-07-21 06:50
yukaAccording to the RE policy the code I have locally is derived from binary RE and someone else should write it again from the information I documented here, but I find it a bit laughable since I narrowed it down to this trivial change.#asahi-re · 2026-07-21 06:50
yukaSo I figured out yesterday, with knowledge gained from binary RE, how to initialize the pcie on t8132/t6040. The main info needed is APCIE_PHY_CTRL_RESET BIT(7) => BIT(4).#asahi-re · 2026-07-21 06:36
yukafirst assumption should be that something is not yet initialized/enabled when getting an SError#asahi-re · 2026-07-21 06:36
yukabut in general, yes#asahi-re · 2026-07-21 06:35
yukait's not that unlikely that they also disable some of the cpu controls that way#asahi-re · 2026-07-21 06:35
svenshutup, Claude :p#asahi-re · 2026-07-21 06:35
yukaexactly :p#asahi-re · 2026-07-21 06:35
JamesCalligeros[m]fabric firewall :p#asahi-re · 2026-07-21 06:35
yukaexactly#asahi-re · 2026-07-21 06:34
svensounds more likely they can just disable some regions or something #asahi-re · 2026-07-21 06:34
yukaas if there's a list of disallowed regions somewhere