You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
</li><liclass=nav-spacer></li></ul></div><p>Linux 6.15 is right around the corner, which means it’s time for another progress
47
+
report! We have been pretty busy behind the scenes and we have some exciting developments
48
+
to share with you all.</p><h2id=fedora-asahi-remix-42-release>Fedora Asahi Remix 42 Release</h2><p>Last time, we announced that Fedora Asahi Remix 42 was close to release. It has since
49
+
<ahref=https://fedoramagazine.org/fedora-asahi-remix-42-is-now-available/>released</a> and is
50
+
now available to install! The Asahi Installer now offers Fedora Asahi Remix
51
+
42 images by default, and existing users on FAR 40 and 41 are encouraged to upgrade using
or Plasma’s Discover to start enjoying the latest versions of your favourite
54
+
software. This is also a reminder that Fedora Asahi Remix follows the <ahref=https://docs.fedoraproject.org/en-US/releases/lifecycle/>Fedora Linux lifecycle policy</a>,
55
+
and thus Fedora Asahi Remix 40 is now fully end-of-life (EOL).</p><h2id=fewer-forks-more-spoons>Fewer forks, more spoons</h2><p>We are pleased to announce that our graphics driver userspace API (uAPI) has been merged
56
+
into the Linux kernel. This major milestone allows us to finally enable OpenGL, OpenCL and Vulkan
57
+
support for Apple Silicon in upstream Mesa. This is the only time a graphics driver’s
58
+
uAPI has been merged into the kernel independent of the driver itself, which was kindly
59
+
allowed by the kernel graphics subsystem (DRM) maintainers to facilitate upstream Mesa enablement while
60
+
the required Rust abstractions make their way upstream. We are grateful for this one-off exception,
61
+
made possible with close collaboration with the kernel community.</p><p>This means that we will soon sunset our Mesa, virglrenderer, and Flatpak runtime forks. Eliminating these forks lightens
62
+
our maintenance burden, and working directly with upstream Mesa improves the development
63
+
experience for folks working on the userspace graphics stack. It also means that other distros
64
+
like <ahref=https://salsa.debian.org/xorg-team/lib/mesa/-/commit/bcd9afe05d2e31459eb8c1f54b6dda2a257cbf14>Debian</a>
65
+
and <ahref=https://github.com/gentoo/gentoo/commit/23e382acf4f7d75e49bc694f409c92385283632f>Gentoo</a>, and
66
+
the <ahref=https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commit/13e0add938f4c74887a08ad0ef6493502a8d3913>Freedesktop SDK</a>
67
+
can provide userspace graphics support for Apple Silicon without any additional packaging burden.</p><p>Fedora Asahi Remix will drop the forked packages with the upcoming Fedora Linux 43
68
+
based release. We expect that to happen without user intervention. The transition will be
69
+
disruptive for Fedora Rawhide, but Rawhide is not supported or expected to be used on end-user systems.</p><p>Upstreaming the uAPI has been an ongoing effort behind the scenes for
70
+
a long time. Making a single change to the uAPI requires commensurate changes to the
71
+
kernel driver, Mesa and virglrenderer. These changes need to be synchronised, since Mesa
72
+
and virglrenderer rely on the uAPI to communicate with the kernel driver. Some keen observers
73
+
may have noticed that <ahref=https://lore.kernel.org/asahi/20250310-agx-uapi-v1-1-86c80905004e@rosenzweig.io/>many</a><ahref=https://lore.kernel.org/asahi/20250313-agx-uapi-v2-1-59cc53a59ea3@rosenzweig.io/>versions</a><ahref=https://lore.kernel.org/asahi/Z-Fn4niI6_Yd06Ze@blossom/>of</a><ahref=https://lore.kernel.org/asahi/20250323-agx-uapi-v4-1-12ed2db96737@rosenzweig.io/>the</a><ahref=https://lore.kernel.org/asahi/20250326-agx-uapi-v5-1-04fccfc9e631@rosenzweig.io/>uAPI</a><ahref=https://lore.kernel.org/asahi/20250327-agx-uapi-v6-1-df6b878a61b2@rosenzweig.io/>were</a><ahref=https://lore.kernel.org/asahi/20250408-agx-uapi-v7-1-ad122d4f7324@rosenzweig.io/>submitted</a> to the kernel mailing lists
74
+
before it was finally merged. Some of the changes between versions were fundamental
75
+
in nature, requiring significant rework to the userspace components and
76
+
kernel driver itself. Alyssa and Janne dedicated countless hours to this endeavour over
77
+
the past few months - making changes, testing them, changing the changes, testing the
78
+
new changes, rinse and repeat. As ever, they have our deepest gratitude and respect
79
+
for pouring so much of their time and effort into closing this out.</p><h2id=even-more-kernel-upstreaming>Even more kernel upstreaming!</h2><p>The past couple of months have also led to even more kernel patches finding their
80
+
way upstream. Linux 6.15 sees the introduction of the Apple Display Pipe (ADP) display
81
+
controller and Z2 touchscreen digitizer drivers, which together enable Touchbar
82
+
support in the upstream kernel for the M1 and M2 13" MacBook Pros.</p><p>Also finding their way upstream are a number of critical patches for supporting various
83
+
functional blocks in Apple’s SoCs. PCIe controller support has been merged for the
84
+
T6020 SoC (M2 Pro), which lays the groundwork for supporting the USB-A ports on
85
+
the M2 Pro Mac mini, as well as WiFi and Bluetooth on all M2 Pro devices. WiFi/BT
86
+
additionally depends upon the System Management Controller. Work is ongoing to get
87
+
the SMC driver upstreamed.</p><p>Linux 6.15 also includes some patches we require for audio, particularly around the TAS2764 and TAS2770 speaker amp chips.
88
+
These patches add basic support for the Apple-specific variants found in Apple Silicon
89
+
Macs.</p><h2id=i-cant-triforce>I can’t triforce</h2><p>Last update, we released microphone support for most laptops. We have since added
90
+
support for the M1 and M2 13" MacBook Pros. Unfortunately, wider release of the microphone
91
+
stack revealed a number of issues. We discovered that the Always-On Processor (AOP) on M2 Pro/Max devices
92
+
differs slightly from the rest of the Apple Silicon family, meaning that microphones
93
+
currently do not work on laptops with those SoCs. Work is underway to sort this out,
94
+
so hang tight!</p><p>As discussed last time, Triforce is my naive attempt at implementing a beamformer with
95
+
minor prior knowledge. In my haste to get something working out the door in a
96
+
reasonable timeframe, I made some questionable, <em>temporary</em> engineering decisions.
97
+
Surely I would have time to undo these soon, right?</p><p>There is nothing more permanent than a temporary solution. Life got in the way, and I
98
+
found myself with no time to rectify the issues. Ah well, performance is pretty
99
+
bad, but it works well enough…</p><p>One of the assumptions I made when building Triforce is that PipeWire’s “quantum” (buffer
100
+
size) will always be 1024 samples. At the time, I thought this would be true on every Apple Silicon Mac. Turns out that was a
101
+
bad assumption. If Triforce sees an input buffer that is smaller than 1024 samples,
102
+
it will return nothing to the graph, effectively muting the microphone.</p><p><ahref=https://github.com/let-def>Frédéric Bour</a> ran into this somehow on Fedora Linux 42, and in
103
+
the process of fixing it also took it upon himself to fix many of the other bad choices
104
+
I made in the course of development. The end result is that Triforce should now be more
105
+
accommodating of oddball PipeWire configurations, and about 4 times faster! A huge
106
+
thanks to Frédéric for picking up my slack on this one.</p><h2id=upcoming-talks>Upcoming talks</h2><p>May brings with it <ahref=https://www.redhat.com/en/summit>Red Hat Summit</a> and
107
+
June brings <ahref=https://devconf.info/cz>DevConf CZ</a>. Asahi will be present at both.
108
+
At RH Summit, Neal and Davide will <ahref=https://events.experiences.redhat.com/widget/redhat/sum25/SessionCatalog2025/session/1731519631980001Xort>present</a>
109
+
Fedora Asahi Remix and CentOS Hyperscale Asahi Remix as accessible platforms
110
+
for developers targeting Linux on ARM64. The <ahref=https://pretalx.devconf.info/devconf-cz-2025/talk/P3TEBA/>talk</a>
111
+
at DevConf CZ will focus on the effort to port CentOS Stream to Apple Silicon.
112
+
Both sessions will be available online.</p><h2id=were-chronically-online>We’re chronically online</h2><p>In addition to our <ahref=https://social.treehouse.systems/@AsahiLinux>Mastodon</a> profile, we now
113
+
have Bluesky and LinkedIn accounts. You can follow us at <ahref=https://bsky.app/profile/asahilinux.org>@asahilinux.org</a>
114
+
on Bluesky, and at <ahref=https://www.linkedin.com/company/asahilinux/>Asahi Linux</a>
115
+
on LinkedIn.</p><h2id=new-distro-guidelines>New distro guidelines</h2><p>Since the beginning of the project, folks from all walks have worked to support Apple
116
+
Silicon in their favourite distros. This immense interest is a gratifying confirmation
117
+
that the community values our work.</p><p>As part of our effort to encourage distros to take up Apple Silicon support, we have
118
+
accommodated all third-party efforts, even allowing distro-specific
119
+
documentation on our project’s website. Unfortunately, this has led to
120
+
an impression that we, as the upstream Asahi Linux developers, are involved
121
+
with or otherwise endorse these efforts. This creates both an expectation
122
+
of support and an impression that these efforts are representative of the state
123
+
of Apple Silicon support, or even the state of the broader AArch64 ecosystem. These expectations are
124
+
a significant and growing burden on us, and we need to address it.</p><p>We have released <ahref=https://asahilinux.org/docs/alt/policy/>guidelines</a>
125
+
outlining our expectations for distros supporting Apple Silicon. These
126
+
guidelines target official distro projects wishing to collaborate directly with us. We will
127
+
never discourage anyone from adding Apple Silicon support to any distro they choose, but we
128
+
cannot offer official support or endorsement to those projects either.</p><p>As a result, we are purging all distro-specific documentation and filtering
129
+
the list of advertised distros to only those which follow the guidelines.</p><p>Our long-term goal remains upstreaming everything such that Apple Silicon does not need
130
+
any special treatment or handling.</p><h2id=infrastructure-ownership>Infrastructure ownership</h2><p>Until recently, most of our infrastructure was under the control of individuals, including
131
+
domain names. Over the past month, we have been working on transferring as much of this
132
+
as possible away from developers’ private accounts and into ownership at the project level.
133
+
This ensures that the project is resilient against any one person leaving.
134
+
It also makes it easier for project expenses to be accounted for. For example, having
135
+
our domain names under the financial ownership of Open Source Collective means that all
136
+
domain-related expenses are processed automatically, rather than needing to paid out
137
+
by a developer and reimbursed.</p><h2id=coming-up-next>Coming up next…</h2><p>We have a few items currently pending review on the mailing list, or merged pending
138
+
release in Linux 6.16. Of particlar note are drivers for the SMC and SPMI controller.
139
+
The SMC is important for system shutdown and reboot, GPIO (required to e.g. power on the WiFi board),
140
+
various hardware monitoring sensors, and the RTC. SPMI is a two-wire serial bus similar to I<sup>2</sup>C.
141
+
Important peripherals, like the power management controller, are attached via this bus.
142
+
Starting with the M3, the USB PD controllers, which negotiate the mode
143
+
(e.g. USB3, Display Port, etc.) with the devices attached to the ports and forward
144
+
it to the PHY and USB controller, are also attached to SPMI rather than
145
+
I<sup>2</sup>C, making the SPMI controller driver essential for supporting
146
+
those devices. We hope to have more to share in the next progress report.</p><p>As always, we want to thank everyone who supports us on <ahref=https://opencollective.com/asahilinux/>OpenCollective</a>
147
+
and <ahref=https://github.com/sponsors/AsahiLinux>GitHub Sponsors</a>. None of this would be possible
148
+
without your generous support.</p><divclass=post-bottom>James Calligeros · <spanclass=publishdate>2025-05-15</span></div></div></div></section><footerid=footer>
149
+
<divclass=footer-menu>
150
+
<divclass=footer-logo>
151
+
<ahref=/>
152
+
<imgsrc=/img/AsahiLinux_logomark.svgclass=logoalt="Asahi Linux logo">
153
+
</a>
154
+
<spanclass=license>Licensed under CC BY-SA 4.0</span>
155
+
<spanclass=disclaimer>Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. All other product names, logos, and brands are property of their respective owners.
156
+
<spanclass=kawaii-disclaimer>Kawaii Asahi Linux logo by <ahref=https://github.com/SAWARATSUKI/Logos>SAWARATSUKI</a> (see link for license).</span>
<li><ahref=/about>About</a></li><li><ahref=/code-of-conduct>Code of Conduct</a></li><li><ahref=/copyright>Copyright policy</a></li></ul></div></div></footer></body></html>
<aclass=post-titlehref=https://asahilinux.org/2025/05/progress-report-6-15/>Progress Report: Linux 6.15</a>
37
+
<summary>Linux 6.15 is right around the corner, which means it’s time for another progress report! We have been pretty busy behind the scenes and we have some exciting developments to share with you all.
38
+
Fedora Asahi Remix 42 Release Last time, we announced that Fedora Asahi Remix 42 was close to release. It has since released and is now available to install! The Asahi Installer now offers Fedora Asahi Remix 42 images by default, and existing users on FAR 40 and 41 are encouraged to upgrade using dnf system-upgrade or Plasma’s Discover to start enjoying the latest versions of your favourite software. <ahref=https://asahilinux.org/2025/05/progress-report-6-15/title="Read more">... </a></summary>
39
+
<divclass=meta>2025-05-15</div></li><li>
36
40
<aclass=post-titlehref=https://asahilinux.org/2025/03/progress-report-6-14/>Progress Report: Linux 6.14</a>
37
41
<summary>As March draws to a close and Linux 6.14 nears release, now is a good time to provide you all with our first major progress update since taking the lead on the project. Going forward, we hope to keep these updates in sync with upstream kernel releases. We feel that this is a natural cadence given the focus on upstreaming, with enough time between posts for noteworthy downstream changes to accumulate. <ahref=https://asahilinux.org/2025/03/progress-report-6-14/title="Read more">... </a></summary>
0 commit comments