#asahi-dev · 2025-08-16 15:11
nickchanT2 SMC from the point of the T2 has ~identical communication format as the M1 SMC. not sure from the intel side but i think that's about the same as non-t2 intel macs?#asahi-dev · 2025-08-13 08:58
nickchanas long as rtc_offset existence is checked in nvmem-cell-names I suppose it is fine#asahi-dev · 2025-08-13 08:57
nickchanso upstream wants to have the smc rtc node folded into parent this might be possible without busting the "apple,smc" compatible#asahi-dev · 2025-08-13 08:55
nickchanfor smc rtc support, there are 3 variants: 1. none at all (A11), 2. 4 byte offset (T2), 3. 6 byte offset (M1-M2)#asahi-dev · 2025-08-09 16:41
nickchanthe only ones where sda has a bigger pin number than scl#asahi-dev · 2025-08-09 16:39
nickchansven: you can pick the i2c dts changes as-is. t8010's i2c2 and i2c3 pins might look out of order but this is really how that hw is like#asahi-dev · 2025-08-08 09:56
nickchanit /should not/ break anything since i checked on t6000#asahi-dev · 2025-08-08 09:55
nickchanhttps://github.com/HoolockLinux/linux/tree/b4/t8015-nvme this is my take on t8015's nvme probably will send when the merge window closes#asahi-dev · 2025-08-05 05:45
nickchanso that settles it#asahi-dev · 2025-08-05 05:45
nickchanthe values read do look sensible but changing them doesn't really work#asahi-dev · 2025-08-05 05:43
nickchanchaos_princess: i did try the cpu frequency stuff myself on t6000 yesterday there's a lock of some sort I think#asahi-dev · 2025-08-04 18:09
nickchanerm I mean cpu performance counter event description here, uncore remains undocumented#asahi-dev · 2025-08-04 18:09
nickchanalso the event descriptions *are* in /usr/share/kpep at least on macOS 15.5 so that doesn't require the optimization guide#asahi-dev · 2025-08-04 18:03
nickchanerm I mean a grand total of two known events obviously there are more events#asahi-dev · 2025-08-04 18:01
nickchanevent 2 seems to be reference cycle and event 3 seems to the mach_absolute_time()#asahi-dev · 2025-08-04 18:01
nickchannow I understand how the Uncore performance counters are supposed to work, but only a grand total of two events#asahi-dev · 2025-08-04 13:53
nickchan*sigh* packit failed on pr 479 and that appears to be a server issue#asahi-dev · 2025-08-04 11:11
nickchanseems to be okay on t6000 as well#asahi-dev · 2025-08-04 11:11
nickchanupdated the two pre-M1 m1n1 PRs and added a third one to address the -march issue found yesterday#asahi-dev · 2025-08-03 16:37
nickchannothing to worry about for upstream then other than the everything compiled for armv8.2-a which is not even the reason things are breaking#asahi-dev · 2025-08-03 16:36
nickchanuart doesn't have that issue so it's an iodev issue after all I will see#asahi-dev · 2025-08-03 16:32
nickchanunforunately that does not fix the issue so I need to look further, probably good idea to keep the change in makefile though#asahi-dev · 2025-08-03 16:27
nickchangot it, add .arch armv8.2-a to all the inline asms and it is fine (the critical ones happen via the sysreg wrapper so it really is just 2)#asahi-dev · 2025-08-03 16:24
nickchanfix the issues here#asahi-dev · 2025-08-03 16:24
nickchanlinux uses -Wa,-march=armv8.4-a -DARM64_ASM_ARCH="armv8.4-a" but that still doesn't fix the #asahi-dev · 2025-08-03 16:18
nickchannah there's also a bunch in src/exception.c but linux must be somehow dealing with all of this #asahi-dev · 2025-08-03 16:13
nickchanugh there's also PAN register but I suppose I could move that to asm files#asahi-dev · 2025-08-03 16:09
nickchanthat makes it a bit easier to deal with#asahi-dev · 2025-08-03 16:08
nickchanokay all the inline sysreg accesses that causes issues when compiled with -march=armv8-a is within the hv files#asahi-dev · 2025-08-03 16:05
nickchanthis could become an issue down the line for macs too if some newer arm msr needed to be accessed#asahi-dev · 2025-08-03 15:58
nickchanand there's inline asm everywhere#asahi-dev · 2025-08-03 15:55
nickchanokay now that's fun because I have to instruct the compiler to not emit lse atomics while still allowing all those sysreg accesses to happen#asahi-dev · 2025-08-03 15:54
nickchanit was never changed#asahi-dev · 2025-08-03 15:46
nickchanand it was not like this#asahi-dev · 2025-08-03 15:46
nickchanit's truly weird#asahi-dev · 2025-08-03 15:46
nickchanjannau: im looking into the behaivor because I cannot reproduce the behaivor on a8 and a11 but can on a7 and a10#asahi-dev · 2025-08-03 15:41
nickchanokay it's not that simple I should look into it more#asahi-dev · 2025-08-03 15:38
nickchanI mean mrs() but both has issues seems anything that ends up calling p.call is problematic#asahi-dev · 2025-08-03 15:37
nickchanthere's some new weird issues right now with the armv8.0 chips (a7-a10,t2) that causes m1n1 to stop responding on the second msr() in two msr() in a row, sounds like atomics :/#asahi-dev · 2025-08-03 13:46
nickchanwouldn't be surprised if there's some atc mishandling#asahi-dev · 2025-08-03 13:45
nickchanSo I suppose I should stick to that#asahi-dev · 2025-08-03 13:45
nickchanokay a usb2 c to c cable works too#asahi-dev · 2025-08-03 13:38
nickchanso I used thunderbolt 4 cable to connect the mbp 2018 15 inch's usb-c port and j314sap's m1n1 proxy together and that does not work but a usb-a to c cable with an adapter worked fine#asahi-dev · 2025-08-03 10:34
nickchanif anything should be a pr_debug#asahi-dev · 2025-08-03 10:33
nickchanthat pmgr misc state driver sounds sane enough other than the printk("set %d ps to pstate %d\n", dev, pstate);#asahi-dev · 2025-08-03 10:32
nickchanmacvdmtool won't work with a t2 host but I suppose I could live without that#asahi-dev · 2025-08-03 10:27
nickchanso I can debug the j314sap#asahi-dev · 2025-08-03 10:27
nickchantime to setup the m1n1 tethered boot setup I guess I can use the t2 mac as the host#asahi-dev · 2025-07-19 14:42
nickchanwouldn't need to think about linux-apfs at least for a while :)#asahi-dev · 2025-07-19 14:42
nickchanalso managed to resize the main apfs container so it's all working nicely