#asahi-dev · 2026-06-03 10:55
StanfordAppliedCyber[m]basically, my current plan is the following things:#asahi-dev · 2026-06-03 10:54
StanfordAppliedCyber[m]i'm at the point where i really need to think about how to upstream the sptm emulator because i'm 100% certain this is going to work and i think is the best option, looking for some maintainer input here#asahi-dev · 2026-06-03 10:50
tryhard[m]until i just rebooted#asahi-dev · 2026-06-03 10:50
tryhard[m]nope, just another retry with the same crash#asahi-dev · 2026-06-03 10:45
chadmedis there anything else in the logs? it looks like it got stuck dealing with a power domain #asahi-dev · 2026-06-03 10:16
tryhard[m]i'm not sure. every probe i was doing already finished before.#asahi-dev · 2026-06-03 10:11
JamesCalligeros[m]What is that blocking work thread doing#asahi-dev · 2026-06-03 10:07
tryhard[m]https://pastebin.com/UQSTd1ZY#asahi-dev · 2026-06-03 10:07
tryhard[m]chaos_princess: any idea why i'm getting this crash? pmp is fully initialized.#asahi-dev · 2026-06-03 07:01
jannauit's not required to create frame pointers for tail calls. as long as the link register is not disturbed you can still return#asahi-dev · 2026-06-03 06:51
Sobek[m](print_regs on x86 would have to account for the return address pushed on the stack, but not ARM ?)#asahi-dev · 2026-06-03 06:51
Sobek[m]For function calls, ARM uses a link register, and you push it on the stack as part of the function preamble, if your function will be overwriting it (callee saved), right ?#asahi-dev · 2026-06-03 06:49
Sobek[m]I agree, I have the same reaction to magic numbers.#asahi-dev · 2026-06-03 06:49
JamesCalligeros[m]Should probably s/256/sizeof(*regs->exc_info)/ or something #asahi-dev · 2026-06-03 06:49
nickchanso after allocating that space and pushing all the registers then the original sp must be location of exc_info + 256#asahi-dev · 2026-06-03 06:48
nickchanstruct exc_info is 256 bytes long#asahi-dev · 2026-06-03 06:48
nickchanSobek[m]: got it now#asahi-dev · 2026-06-03 06:47
Sobek[m](If ARM stack grow down (I'm sadly more of an x86 person), this would be the top of the stack before pushing 32 64-bit registers in a buffer whose address is in regs ?)#asahi-dev · 2026-06-03 06:45
Sobek[m]What's the type of regs ? Is it possible, that regs is a pointer to somewhere on the stack, and that this is computing an offset from the start of this buffer to compute the stack pointer ?#asahi-dev · 2026-06-03 06:42
nickchantrying to find where that come from#asahi-dev · 2026-06-03 06:42
nickchanwhy u64 sp = ((u64)(regs)) + 256;#asahi-dev · 2026-06-03 06:41
nickchani am confused about print_regs#asahi-dev · 2026-06-03 05:30
AnirbanBose[m]this the right docs i believe #asahi-dev · 2026-06-03 05:30
AnirbanBose[m]https://asahilinux.org/docs/sw/m1n1-user-guide/#asahi-dev · 2026-06-03 05:28
AnirbanBose[m]You: can any provide me the docs and repo where the dev work is going on #asahi-dev · 2026-06-03 05:28
AnirbanBose[m]You: hello I have a m4 air lying around I could help with the m1n1 bootloader stuff i believe #asahi-dev · 2026-06-02 21:35
yukaand *t6030#asahi-dev · 2026-06-02 21:35
yuka*measure pstate latencies#asahi-dev · 2026-06-02 21:35
yukajannau if you want to measure clocks on t8122 or t6031, try this branch: https://github.com/yuyuyureka/m1n1/commits/pstate-latencies-boot-cpu/ (you need the cregs and number of pstates but the rest should work now)#asahi-dev · 2026-06-02 21:01
JamesCalligeros[m]Theyll definitely need separate entries in macaudio and speakersafetyd too#asahi-dev · 2026-06-02 21:01
JamesCalligeros[m]If the ts parameters differ then they will likely need separate tunings#asahi-dev · 2026-06-02 20:55
chaos_princessand 24 seems unique#asahi-dev · 2026-06-02 20:55
chaos_princess24, vs 28 on j514#asahi-dev · 2026-06-02 20:54
chadmedshould be in the ADT#asahi-dev · 2026-06-02 20:54
chadmedcheck to see if it has a different AID#asahi-dev · 2026-06-02 20:53
jannauprobably close enough to to j514. the missing cutout for the usb-c port on the right side hopefully make not much of a difference#asahi-dev · 2026-06-02 20:52
chaos_princess14 inch mbp with non-pro/max chip#asahi-dev · 2026-06-02 20:51
chaos_princessi mean the j504#asahi-dev · 2026-06-02 20:51
chadmed(neo notwithstanding) #asahi-dev · 2026-06-02 20:51
chadmedi suspect it's probably all the same as the m2 machines though#asahi-dev · 2026-06-02 20:51
chadmedpossibly. we'll need to see if there's new TS parameters and new tunings required#asahi-dev · 2026-06-02 20:49
chaos_princessbut we have a new chassis, right?#asahi-dev · 2026-06-02 20:49
chadmedgood news to wake up to :) #asahi-dev · 2026-06-02 20:49
chaos_princessseems to be the same#asahi-dev · 2026-06-02 20:48
chadmedchaos_princess: did you need to make any material changes? nco, admac, mca all the same? #asahi-dev · 2026-06-02 20:36
jannauI've tagged and pushed asahi-7.0.11-1 (bare minimum to get all 14.x based m3 devices to be self-updatable). depends on m1n1 t603x pcie support#asahi-dev · 2026-06-02 19:38
chaos_princessand, it sings, ucm was the missing bit#asahi-dev · 2026-06-02 19:21
Psil0Cybin[m]? why the kik? lol#asahi-dev · 2026-06-02 19:19
chaos_princessmate, stop promoting veganism in front of pork farmers#asahi-dev · 2026-06-02 19:19
Psil0Cybin[m]plus if you want to be a sneaky cat, once the hard drive is gone, no one knows that you know how to use that OS..... ;)