>.. macOS only ever programs CS42L84 to operate at either 48 or 96 kHz, we could only add support for those two sample rates to the Linux driver ..<p>> However, CS42L42 supports all the other common sample rates, and while the register layout and programming sequence is different, the actual values programmed in for 48 and 96 kHz are the same across both chips. What would happen if we simply took the values for all other sample rates from the CS42L42 datasheet and added those to the CS42L84 driver? As it turns out, you get support for those sample rates!<p>> The patch to enable hardware support for 44.1, 88.2, 176.4 and 192 kHz sample rates on both the input and output of the headphone jack was submitted directly upstream, and has been merged for 7.1. We also backported this to Asahi kernel 6.19.9, allowing users to take advantage of this immediately.<p>Nice bit of chip sleuthing and reverse engineering from the Asahi team!
When I think about it, I don't understand why Apple wouldn't want to help this effort and just provide all the documentation.<p>All the classic reasons ("competitive advantage", "secrets", etc) do not hold water in this day and age.
I was trying to come up with a response but you're right. It would be easy for Apple and Apple would get so much goodwill from the community in return.
One of the reasons I can see is it’s much easier to say “we don’t play this game” than get a lot of negative press for selective openness and breaking compatibility of non-public interfaces. Maybe it’s even more important internally, as it enables new kind of internal discussions distracting from priority work.
I imagine the real reason is that if they change things they now have an obligation to promptly share technical docs and if they're slow people will whine and bitch online about them. Not worth it. They have zero to gain (and I say this as someone who would love to dual boot Linux on my M4).
The cynical take is that they make a shit ton of money from services and Linux running on a MacBook won’t help them do that.
The vast majority of people that buy Macs for the ecosystem aren't going to switch to Linux. That market will remain untouched. Outside of a few gamers who might want to put up with the x86-to-ARM translation layer and (for most A to AAA games) Proton to run some non-Mac games. And even they'll probably still dual-boot.<p>There's a portion of another market: people who want to run Linux and want a powerful laptop who buy x86 Laptops right now. Apple could expend very little relative effort while offering no official support by helping Asahi get that to a first class platform. They won't capture them in the ecosystem (and they never would have) but will still benefit from hardware sales to them.<p>Obviously, if they sold their hardware at a loss and subsidized that with ecosystem capture that would be a non-starter. But from everything we know, the hardware itself is very profitable.
Yeah, and having the only supported OS be MacOS means they can entice people to upgrade when they want. No continuing on with 8+ year old hardware and a lightweight Linux distro even if it's fine for the intended use case.
They do also make a lot of money selling hardware, and as things stand today that business happens to make them look like the first tech giant to actually profit from the AI boom (because the hardware they've been developing internally for years happens to be among the best consumer-grade options for self-hosting LLMs). Making their hardware more attractive to tinkerers could be a winning move right now.
This, but also you would be allowing people to learn Linux. Developer with a Mac has to be one of the most common linux defectors. I suspect most people don't realize how doable and comfortable the switch can be.
Linux users don't pay for anything anyway
> I don't understand<p>We really need to retire this phrase, it’s become a humblebrag way of calling the other party delusional without even trying to understand.<p>The list here though is long: priorities, accuracy concerns, blurring the line on official support, IP restrictions with third parties (even Apple uses plenty of licensed cores), etc.
These kind of project reports showing consistent breakthroughs and clearly a finger on the pulse of what users are encountering as pain points are a good indication that the Asahi team are real pros :)<p>Look forward to switching back to Asahi full time soon!!
"Amaze, amaze, amaze!"<p>I wonder if there would be interest in an Asahi Remix spin focused on a more Mac-like out-of-the-box experience: cmd as the main modifier key, Mac-like keyboard shortcuts, theming, gestures, etc.<p>Of course, you can tweak any distro however you want, but I think a curated default experience is a different thing.
I'm glad they dropped the ban on HN readers[1]. That was my very first impression of Asahi Linux that I ever encountered and it's unfortunately what I think of every time I see it show up here.<p>[1] <a href="https://github.com/AsahiLinux/AsahiLinux.github.io/commit/e0484c04ade0e7e5ec3e07179545afabd0ffa765" rel="nofollow">https://github.com/AsahiLinux/AsahiLinux.github.io/commit/e0...</a>
Does anyone knows if it runs on M4 Mac machines?
It runs only on M1 and M2. M3 is being worked on.
<a href="https://asahilinux.org/docs/platform/feature-support/m4/" rel="nofollow">https://asahilinux.org/docs/platform/feature-support/m4/</a>
Fascinating project like always. Thank you Asahi team!
Is there an equivalent of this for iphones so we can give them a second life?
Unfortunately iPhones have locked bootloaders that prohibit installing other operating systems. People <i>have</i> gotten Linux running on iPhones, but it requires jailbreaking and that has gotten much harder over time. And it's not really worth putting effort into developing an OS if nobody is going to be able to install it.
Running what exactly? Older iOS versions? Android?
[flagged]