Про ИТ Коротко - dvperv RSS: главное · RSS: лента

Well here we are again. Linux 7.3 is out and it’s been an eventful few months, so let’s get stuck in to another Asahi Linux progress report! Upstreaming continues As always, upstreaming work continues to progress. Aside from the usual patches for low-level SoC blocks, two major drivers made it on to the list this cycle: macaudio and avd. Getting macaudio ready for submission has been a challenge. The audio subsystem on Apple Silicon devices is rather special, and required quite a number of core ALSA changes to properly support it. Apple also uses special variants of speaker and headset amplifiers that were already supported upstream, and these drivers also needed some pretty significant modifications. We have previously discussed a lot of this work at length, and we are finally in a position where we can submit the main driver for review. The driver and Devicetree changes represent a hefty chunk of our total patchset, about 3100 lines. AVD is a whole different beast. The AVD driver has spent barely 3 months in our downstream tree and is already on the list. This is our shortest turnaround time yet for a major SoC component and bodes well for a transition to upstream-first development some time in the future. This is fantastic news, as the AVD driver and related Devicetree changes are around 13000 lines of code. Also making an appearance on the list this cycle are intial Devicetrees not only for M4 Pro and Max devices but also M5 thanks to Yureka’s tireless efforts. As usual these initial Devicetrees are barebones and only sufficient to boot the SoC to a TTY, however work is progressing on further enablement. Watch this space! We have also begun shifting to an upstream-first approach where practical. Changes to the TI USB-PD and SPMI drivers required for new devices, as well as initial support for Thunderbolt, were all developed upstream-first. We are so thrilled to see our focus on upstreaming starting to pay off! M3 goes GA Last time, we announced initial support for M3 series machines via the EXPERT flag on the Asahi installer. We are pleased to announce that we received almost no issues from early adopters, so M3 support is now generally available without the EXPERT flag! We have also made a number of improvements to M3 support, most notably enabling DCP. On top of performance and battery life improvements, this also allows us to enable sleep on M3 series devices and make the area around the notch useable on the MacBooks! Keep an eye out for m1n1 and kernel updates in the coming days. Crowded House Last time, we teased support for virtualising SPTM-enabled versions of macOS in m1n1, which enables reverse engineering on M4 series machines. M5 presents a new challenge, as the versions of macOS which support it all require the use of Exclaves. Exclaves are small applications running in an isolated environment controlled by the Secure Kernel. On M5 series SoCs and above, macOS uses them for sensitive tasks such as drawing the “camera in use” indicator to the screen. XNU communicates with the Secure Kernel and its Exclaves via SPTM, using yet another IPC protocol called Tightbeam. Much as with SPTM, XNU will panic if it cannot find the running Exclaves. This is all starting to look very similar in concept to Arm’s own TrustZone feature. While some Exclaves can be bypassed by changing some settings on the command line, we predict that this will not always be the case. As such, Sven started looking at how we could fit all of this in to m1n1. First line of investigation, try putting the Secure Kernel and Exclave userspace in another VM next to SPTM and macOS. Oh, that worked, and we’re now up to spawning three VMs in EL1 under m1n1! Maybe we can start selling m1n1 to companies fleeing VMWare… With that, we can now virtualise and reverse engineer macOS on both M4 and M5 series machines. Hello Triangle(s)! While M3 support is now mostly at feature parity with M1 and M2, the very obvious exception to this is the GPU. Apple’s GPU team seems to follow a tick-tock model, and the M3’s GPU was a very significant departure from the models found on M1 and M2 SoCs. We mentioned quite some time ago that the M3 GPU was being reverse engineered by a new group of contributors, however not much has been said since. At XDC this year, Alyssa Millburn, Anna Maniscalco and TellowKrinkle gave a talk on their progress reverse engineering the M3 GPU. Work has progressed far enough for m1n1 to successfully initialise the GPU and for the team to draw a triangle! Fans of the “Think Different” sections of these progress reports will find the talk edifying; Apple have once again made a number of… interesting choices which will require significant engineering effort to integrate into upstream Mesa. It is well worth a watch if you’re interested in more detail. A huge thanks goes out to everyone who has made this work possible. More progress is on the way, so stay tuned. Kept you waiting, huh? All the way back in January of 2024, we made the mistake of promising Thunderbolt support within the year. It’s a mistake we won’t quickly repeat. We’ve said almost nothing about Thunderbolt in the two years since, which begs the question: where is it? Thunderbolt was originally developed by Apple and Intel, with Intel handling the design and fabrication of the hardware required. Since Intel made these controllers available to anyone who wanted them at a (mostly) reasonable price, no one else bothered to design their own. It is only very recently — largely coinciding with the transfer of the standard to the USB-IF — that companies like AMD have decided to roll their own controllers. Apple is of course no exception. As part of their push for insourcing most silicon IP, Apple made the choice to design their own Thunderbolt controller before most others. Surprising no one, the controller is of course a Cortex-M3 running RTKit coupled with a bespoke Thunderbolt/USB4 router. There is one of these for each Thunderbolt-enabled USB-C port on