#
#asahi-dev · 2025-03-15 17:34
nicolas17I don't think PPL is involved in that ;)
#asahi-dev · 2025-03-15 17:30
fl0_idyeah maybe it has to be brute forced, no idea how else ppl found it
#asahi-dev · 2025-03-15 17:09
mischa85or even better just create a function that allows me to set the cpu_start_off variable
#asahi-dev · 2025-03-15 17:06
mischa85then i can brutefore it from shell
#asahi-dev · 2025-03-15 17:06
mischa85i'll just alter smp_start_secundaries so can give it the start_off argument
#asahi-dev · 2025-03-15 16:57
mischa85desperate times
#asahi-dev · 2025-03-15 16:57
mischa85or can run on just the boot cpu maybe....
#asahi-dev · 2025-03-15 16:52
mischa85i tried CPU_START_OFF_T6031 0x88000 but it's incorrect
#asahi-dev · 2025-03-15 16:51
fl0_idwhoop whoop
#asahi-dev · 2025-03-15 16:46
mischa85next destination hv
#asahi-dev · 2025-03-15 16:42
mischa85how can i find CPU_START_OFF_T6041?
#asahi-dev · 2025-03-15 15:45
mischa85maz: patch mailed
#asahi-dev · 2025-03-15 14:52
sventhanks
#asahi-dev · 2025-03-15 14:49
jannaupower is reported with f32 / flt
#asahi-dev · 2025-03-15 14:48
jannausven: "ioft" are iirc temp sensors which we did not use. I see "TG[012][BCHV]", "TR0Z", "TR[12]d" on j314. see proxyclient/experiments/smc.py to dump all keys
#asahi-dev · 2025-03-15 14:42
sven(i'm adding documentation to SMC before trying to upstream it once more)
#asahi-dev · 2025-03-15 14:42
sveni found "SMC returns power in Watts with acceptable precision to scale to uW" in hwmon but dunno if that's f32 or ioft
#asahi-dev · 2025-03-15 14:42
svenjannau: / chadmed: do you have an example for a f32 and a ioft / fixed point key we read from SMC that has to be scaled?
#asahi-dev · 2025-03-15 14:13
mischa85maz: i'll clean up my code and send it to you
#asahi-dev · 2025-03-15 14:13
mischa85that is a significant improvement
#asahi-dev · 2025-03-15 14:12
mischa85well the central scrutinizer happily does 1.5 mbaud
#asahi-dev · 2025-03-15 10:51
mischa85never mind i was being derp
#asahi-dev · 2025-03-15 08:53
fl0_idnickchan thx
#asahi-dev · 2025-03-15 08:24
mischa85i'm not sure i understand what's actually going over the line
#asahi-dev · 2025-03-15 08:23
mischa85hmmmm. i made a fancy eavesdropper for the P_SET_BAUD message that proxy.py does, but the data is packed or something?
#asahi-dev · 2025-03-15 04:58
nickchan>s3_1_c15_c1_5 is _EL1, s3_4_c15_c14_5 is probably _EL2 and s3_4_c15_c14_6 is probably _EL12
#asahi-dev · 2025-03-15 04:52
nickchanand as I said before some new registers like the one that controlled timer frequency has VHE schematics which is another source of confusion
#asahi-dev · 2025-03-15 04:51
nickchanand the next one s3_0_c15_c2_4 should be HID31?
#asahi-dev · 2025-03-15 04:50
nickchanfl0_id: s3_0_c15_c2_3 should be HID30
#asahi-dev · 2025-03-15 00:32
ece3143789253554I posted my patch set for APFS support: https://lore.kernel.org/linux-fsdevel/20250314-apfs-v1-0-ddfaa6836b5c@ethancedwards.com/T/#t
#asahi-dev · 2025-03-14 21:35
fl0_idbut no matter
#asahi-dev · 2025-03-14 21:35
fl0_idmischa85 yeah but I assume in general, better C, architecture and stuff probably based on your github, but ofc just guessing. I feel like I wouldn't even know what to throw or would a lot more trial and error and reading up on architecture etc maybe
#asahi-dev · 2025-03-14 21:32
mischa85110 mbyte on dialup speeds is no joke
#asahi-dev · 2025-03-14 21:32
mischa85just putting together the last bits of the cs-sw hack so i get to use the scrutinizer on steroids
#asahi-dev · 2025-03-14 21:31
mischa85the tooling is put together very structural so that helps a lot
#asahi-dev · 2025-03-14 21:30
mischa85i barely know what i'm doing actually, i'm in the throwing spaghetti at the wall and seeing what sticks phase
#asahi-dev · 2025-03-14 21:28
fl0_idsven ok yeah i can do that, I think
#asahi-dev · 2025-03-14 21:27
fl0_idand thanks
#asahi-dev · 2025-03-14 21:27
fl0_idmischa85 yeah but you probably know more in general
#asahi-dev · 2025-03-14 21:25
sven(in m1n1 that is, kernel stuff should directly go upstream)
#asahi-dev · 2025-03-14 21:25
svenyeah, even if it's not fully working yet i'm happy to merge anything that looks reasonable and gets us closer to m3+
#asahi-dev · 2025-03-14 21:24
mischa85you should be a little less lost than i am, but just in case
#asahi-dev · 2025-03-14 21:24
alyssa(to be clear - i am very happy to see m3+ stuff in m1n1 c: )
#asahi-dev · 2025-03-14 21:23
mischa85fl0_id: if it helps you, my messing around with the chickens is in my m1n1 branch: https://github.com/mischa85/m1n1/tree/t6041
#asahi-dev · 2025-03-14 21:21
alyssa^^
#asahi-dev · 2025-03-14 21:20
svenbut yeah, if you fix all that feel free to open a new one
#asahi-dev · 2025-03-14 21:20
sveni think that pull request also suffered from a-ramses not squashing stuff like clang format fixes
#asahi-dev · 2025-03-14 21:20
fl0_id(which was basically just adding the t6030 define there)
#asahi-dev · 2025-03-14 21:19
fl0_idThen could I resubmit it for merging? (a-ramses did most of that work, I just resolved the conflicts by moving macros/defines to midr.h)
#asahi-dev · 2025-03-14 21:19
svenand honestly, it's code that's called once and lives in its own file. it's allowed to be ugly :D

plus ›