#
#asahi-dev · 2024-10-24 14:45
nickchanbecause with exclaves, sptm and txm macOS by default would have stuff in EL2, EL0, GL2, GL1(!) and GL0
#asahi-dev · 2024-10-24 14:44
nickchanespecially on m1
#asahi-dev · 2024-10-24 14:44
nickchansven: Don't think the exclaves stuff is deployed on macOS yet but after that happens running macOS in hypervisor is going to be... interesting to say at least
#asahi-dev · 2024-10-24 14:37
nickchanwithout demoting
#asahi-dev · 2024-10-24 14:37
nickchanbecause ktrw on a11 *has* to work somehow
#asahi-dev · 2024-10-24 14:37
nickchansven: that must be a recent addition
#asahi-dev · 2024-10-24 14:36
sveniirc you can see PC but not much else
#asahi-dev · 2024-10-24 14:35
svenyeah, it partially works
#asahi-dev · 2024-10-24 14:29
nickchanwhen not demoted I think coresight also doesn't work correctly
#asahi-dev · 2024-10-24 14:26
nickchanhowever, I think it has some compatibility problems and does not work for latest macOS
#asahi-dev · 2024-10-24 14:26
nickchanthe workaround for apple silicon mac would be to run to run macOS in hypervisor on m1n1
#asahi-dev · 2024-10-24 14:25
nickchandavid: it's a software restriction where some demotion registers (needed to enable debugging) disabled by boot ROM
#asahi-dev · 2024-10-24 13:06
davidhardware-level mitigation implemented in the new architecture? If it is a software level then what are the hacky way to achieve this?
#asahi-dev · 2024-10-24 13:06
davidHey, In the past, Intel-based Macs allowed for active kernel debugging, but with the transition to Apple Silicon, developers are now limited to analyzing memory dumps, as outlined in the KDK (Kernel Debug Kit) README for two-machine debugging. Is this limitation on active kernel debugging in Apple Silicon systems the result of a software-level restriction, or does it stem from a
#asahi-dev · 2024-10-17 10:01
allmazzhey! does anyone working on support for displays over usb-c?
#asahi-dev · 2024-10-16 05:38
LarstiQfl0_id: sure
#asahi-dev · 2024-10-16 04:20
al_hi. anyone tried macbook air m3? i know officially it's not supported -- just uart/keyboard/framebuffer is enough for me for now (working hypervisor would be amazing to have too!)
#asahi-dev · 2024-10-15 16:19
fl0_idLarstiQ but usable, mostly. sth like a legacy app with nothing on the web is much harder to replace
#asahi-dev · 2024-10-15 15:58
nickchansomething like 2400 MHz is a lot more stable though
#asahi-dev · 2024-10-15 15:53
LarstiQthey're not entirely equivalent with the web version
#asahi-dev · 2024-10-15 15:01
chaos_princessall of those are electron wrappers, just use the web version
#asahi-dev · 2024-10-15 15:00
m3thostalking about generic x86 windows application support, that woud be very much appreciated. there are a bunch of applications (closed source) that aren't released for linux-arm64, for example: Slack, Zoom, Discord
#asahi-dev · 2024-10-15 14:51
nickchanprobably because i didn't mess with the other fields
#asahi-dev · 2024-10-15 14:51
nickchanthough i must say that state is very unstable
#asahi-dev · 2024-10-15 14:48
ariejancy8aer thanks for the update. I'll try to find it in the logs.
#asahi-dev · 2024-10-15 14:42
nickchanand see if those states are the same now
#asahi-dev · 2024-10-15 14:41
nickchana safe test would be to say, overwrite the definition of pstate 3 with defintion of pstate 4
#asahi-dev · 2024-10-15 14:41
nickchannot sure if they are locked down on m1
#asahi-dev · 2024-10-15 14:36
nickchanthe cpu ratio is multiplied with the 24 MHz clock to get the final frequency
#asahi-dev · 2024-10-15 14:35
nickchanhaven't figured other fields and psinfo2 yet but presumable has to do with core and sram voltage
#asahi-dev · 2024-10-15 14:35
nickchanon a10 the cpu ratio is (((psinfo1 & 0xffffffff) >> 0xe) & 7) / 5 + ((psinfo1 >> 4) & 0xff) / ((psinfo1 & 0xf) * 2 + 2)
#asahi-dev · 2024-10-15 14:34
nickchanso yeah that's an overclock primitive
#asahi-dev · 2024-10-15 14:33
nickchanin the example above I am modifying the definition of pstate 1
#asahi-dev · 2024-10-15 14:33
nickchanso like what frequency and voltage pstate N is
#asahi-dev · 2024-10-15 14:32
nickchanwhich allows arbitrary changes in meaning of the pstates
#asahi-dev · 2024-10-15 14:31
nickchanthat register (at a different offset) on a10 seems to be writable
#asahi-dev · 2024-10-15 14:31
nickchanthe register that corellium called CLUSTER_PSINFO1_GET() and CLUSTER_PSINFO2_GET() in linux-m1
#asahi-dev · 2024-10-15 14:30
nickchanusing modified proxyclient/experiments/cpu_pstates.py
#asahi-dev · 2024-10-15 14:29
nickchanmeasured cpu frequency reached 2508 MHz
#asahi-dev · 2024-10-15 14:27
nickchanresult:
#asahi-dev · 2024-10-15 14:27
nickchan>>> write64(0x202f00000 + 0x20020, 1 << 25 | 1 | 1 << 12)
#asahi-dev · 2024-10-15 14:26
nickchan>>> write64(0x202f00000 + 0x80000 + 0x20 * 1, 0xae00000404a20dc0)
#asahi-dev · 2024-10-15 14:26
nickchan>>> write64(0x202f00008 + 0x80000 + 0x20 * 1, 0x50000f8c0a000606)
#asahi-dev · 2024-10-15 14:26
nickchan>>> write64(0x202f00000 + 0x20020, 1 << 25 | 2 | 2 << 12)
#asahi-dev · 2024-10-15 14:26
nickchanon a10:
#asahi-dev · 2024-10-15 13:40
chadmedits all very odd
#asahi-dev · 2024-10-15 13:40
chadmedits also unclear how the microphone array is actually supposed to work. there are three mics in the laptops but two of them seem acoustically coupled to the chassis or something
#asahi-dev · 2024-10-15 13:39
chadmedthere is no sane way to replicate what coreaudio has for that in linux without more stupid custom plugins
#asahi-dev · 2024-10-15 13:39
chadmedthe beamforming and noise cancellation stuff is a pain
#asahi-dev · 2024-10-15 13:34
cy8aerariejan: As I understand the main problem is not the microphone hardware support itself but the beam forming stuff. And in this channel chaos_princess talked about it some month ago.

plus ›