#asahi-dev · 2026-10-25 17:29
sofusthe probe of the actuator. I will give you a small example by what i mean, but im really not sure its correct/better#asahi-dev · 2026-10-25 17:14
hex86[m]*magicmouse instead of putting it into the actuator#asahi-dev · 2026-10-25 17:13
hex86[m]Do you mean putting it into the probe of the magicmouse or actuator?#asahi-dev · 2026-10-25 17:13
hex86[m]By the way, could you clarify what is meant by https://github.com/AsahiLinux/linux/pull/573#discussion_r4371104043 ?#asahi-dev · 2026-10-25 17:13
hex86[m]sofus: Yeah I think so, and even the magicmouse.c file itself is really different from upstream, I have no idea how to even start with handling all of that.. #asahi-dev · 2026-10-25 16:39
sofusTechnically the driver depends on magic-mouse having mtp thing, but maybe that can just be ignored. If the dockchannel-hid driver works with the actuator, maybe its enough to simply write 'depends on: xxx'#asahi-dev · 2026-10-25 16:38
sofusAmazing! Im not super familiar with how to handle dependencies. The dockchannel-hid driver which i imagine is the biggest pre-requisite, is activly being upstreamed#asahi-dev · 2026-10-25 16:27
hex86[m]and the magicmouse / apple hid drivers get a patch every so often anyways, as they're used for non-macbook devices too, and so finally getting these upstreamed would probably help reduce asahi maintainence burden too :D#asahi-dev · 2026-10-25 16:26
hex86[m]I'd really like to take on the work of getting the pre-requisite patches upstreamed, I've submitted to the kernel before but I've never tried upstreaming patches from kernel forks, and I'd like to get experience on that, but I might need some advice because I've never tried#asahi-dev · 2026-10-25 16:25
hex86[m]So I don't even know how I'd get started on getting these upstreamed 😅#asahi-dev · 2026-10-25 16:24
hex86[m]But I think a lot of the pre-requisite patches that lead up to it haven't been upstreamed yet#asahi-dev · 2026-10-25 16:24
hex86[m]and to answer your question, I would really like to get it upstreamed; There's basically nobody using the haptic functionality in the kernel right now (See: Libinput) and so having more of the haptic functionality actually in the kernel would definitely help push adoption#asahi-dev · 2026-10-25 16:24
hex86[m]Working through it now#asahi-dev · 2026-10-25 16:24
hex86[m]sofus: Thank you so much for the feedback!#asahi-dev · 2026-10-25 16:12
svenjust this MTE crap but that shouldn't be there on a18 pro I think#asahi-dev · 2026-10-25 16:12
svenno idea why, haven't run into an SError on m5 so far#asahi-dev · 2026-10-25 16:08
snooze6214[m]:( im stuck with the serror again #asahi-dev · 2026-10-25 16:04
sven*sigh* yeah... this is some MTE crap#asahi-dev · 2026-10-25 15:53
svendump ELR_EL12, ESR_EL12 and FAR_EL12#asahi-dev · 2026-10-25 15:52
svensnooze6214[m]: and yeah, that looks like a panic loop. could even be SPTM's panic loop that early#asahi-dev · 2026-10-25 15:51
sveni guess m5 hv even without secure kernel is gonna be "fun" *sigh*#asahi-dev · 2026-10-25 15:51
svensnooze6214[m]: ah.. the other cores might not even be up i think. otherwise cpu(n) and then context()#asahi-dev · 2026-10-25 15:50
svenhttps://fuzzinglabs.com/wp-content/uploads/2026/05/Navigating_iOS_MTE_Landscape.pdf which points to that... MTE crap :-(#asahi-dev · 2026-10-25 15:50
snooze6214[m]sven: how do i dump state of all cores with m1n1? i seem to be stuck spinning, also there's some strings pointed by the registers so i might be stuck in some error handler? https://termbin.com/mmyt#asahi-dev · 2026-10-25 15:50
svenTagOffset_EL2 according to debug strings I think...#asahi-dev · 2026-10-25 15:47
svenhrm, looks like it fault trying to read S3_0_C11_C9_0#asahi-dev · 2026-10-25 15:40
sventhat only matters once it's far into xnu#asahi-dev · 2026-10-25 15:40
yukaah fair#asahi-dev · 2026-10-25 15:40
sveni've just disabled the amcc stuff for now#asahi-dev · 2026-10-25 15:40
yukanot sure if that matters at this stage#asahi-dev · 2026-10-25 15:40
yukaand you might want amcc-plane-enable-mask?#asahi-dev · 2026-10-25 15:40
yukasven: in the M5 adt you sent me, it also has amcc-enable-mask = 1, amcc-plane-enable-mask = 15#asahi-dev · 2026-10-25 15:39
sventried to boot the hv on m5 and it hangs very very early inside SPTM :(#asahi-dev · 2026-10-25 15:38
jannauI assume it's different builds of the same kernel. maybe turning some debug builds on and possibly less optimizing compiler#asahi-dev · 2026-10-25 15:31
yukaand the documentation explicitly mentions kernel.development.*.dSYM which no longer exists#asahi-dev · 2026-10-25 15:30
yuka> it's also helpful if you have a development kernel with symbols#asahi-dev · 2026-10-25 15:30
yukaI asked since sven said:#asahi-dev · 2026-10-25 15:30
yukawhat is the difference between release and development kernel for our purposes?#asahi-dev · 2026-10-25 15:30
yukaYes#asahi-dev · 2026-10-25 15:29
jannauthe 26.7.1 KDK still has *.dSYM dirs for the kasan and release kernel#asahi-dev · 2026-10-25 15:17
yukais it possible that the symbols are somehow included in the kernel.development.*?#asahi-dev · 2026-10-25 15:16
svenmaybe i'm just misremembing and looked at a previous kernel then#asahi-dev · 2026-10-25 15:16
svenhrm, can't find it anymore#asahi-dev · 2026-10-25 15:05
svenlet me check again#asahi-dev · 2026-10-25 15:05
svenbut i though i had some symbols at least for macos 27 on m1#asahi-dev · 2026-10-25 15:05
svenugh.. that's annoying :(#asahi-dev · 2026-10-25 15:04
yukathe kernel.development.*.dSYM dirs are no longer included in the KDK#asahi-dev · 2026-10-25 15:03
svendon't they have a KDK for those already?#asahi-dev · 2026-10-25 15:03
yukahow do you get the symbols for macOS 26 / 27