Even my job - I write web apps, I don't need a GPU. If it can play audio through a headphone jack, and draw a window nicely without aggravating amounts of tearing (though I might work in a full-screen CLI anyway), I don't care, it's Linux!
[Edit: I'm not disputing a GPU is nice to have. I am dismissing the overly negative reply above.]
An M1 with Asahi looks fantastic to me.
Yes, the browser engine that had to be forked because Apple neglected it for so long. Brilliant example!
> and also brought us CUPS
Nope. That would be Michael Sweet. Apple later hired the main developer behind the effort, and adopted the standard as their own. Same thing happened with LLVM, so don't go around spreading those particular lies.
Got anything else? All of your examples seem to be instances where Apple has neglected Open Source or just threw money at something they were incapable of competing with.
> there's Apple code in your Linux distribution for everyday functionality, gasp!
Man, wait until you hear who contributed the POSIX APIs, SMP support, multitasking/multiuser functionality and the entire networking stack to MacOS... ;)
I do think Apple’s open source contributions are largely undersold, although they’ve probably contributed less than other technology companies their size (e.g. Google).
GUIs will essentially emulate the GPU in software and reduce battery life.
GPUs are also more power efficient at many of these things, because while they use more power while running they get done sufficiently quickly that they end up ahead. That’s before you include the power savings from rapidly dropping the power mode.
Note that this isn’t specific to AS, or even arm in general: every laptop wants to get to low power as fast as possible, because constant low-ish power is much worse than brief spikes that you can disable power between.
The only reason modern laptops have 10h+ battery life is because of GPUs. Sure, without it you can manage, your power efficiency will just massively tank.
However, this could be absolutely amazing for the new M1 desktops, or for the M1 Mac Mini. It could make a kick-ass server.
Did I mention the hardware is just that good? :-)
Seriously though, you’re all doing a very impressive work!
Then how did Integrated Graphics sell so well in the broader marketplace? You'd think with their near-useless GPUs that were weaker than M1's software rendering that nobody could use them.
Also, whatever about M2 - Apple has structured their hardware to require minimum driver changes on each release. M2 will probably just be a few patches on the core driver, not a rewrite.
The point is to delegate rendering away from the GPU, which is obviously a waste of compute no matter how you look at it. Every computer is capable of software rendering (my i5 520m can software-render for crying out loud), but we live in a more civilized age; even weak GPUs do their job to prevent the CPU from being unnecessarily bogged down with a task it's not good at. We do this so your computer doesn't insta-break when you plug in an external display, we do this so that CPU cores don't get pinned when you start scrolling a webpage, we do this because software rendering is bad. It doesn't matter if you're doing it on an i9 12900k or a first-gen Raspberry Pi; the goal is to not waste CPU cycles on it in the first place. This shouldn't even be up for debate in the first place.
This is making a lot of leaps. None of his comments say that. They have a whole page [0] dedicated to a nuanced discussion on "when will Asahi Linux be done". It's perfectly fine for him to be excited about his project and his hardware. Lots of other people are also excited, which is awesome!
[0]: https://github.com/AsahiLinux/docs/wiki/%22When-will-Asahi-L...
This is not to say GPU support is a long way away; it isn't.
> and that we may well have an M2 on store shelves before you've even got M1 support to a usable point.
You're assuming M2 will take another year. M1 Pro and Max took a week or so to bring to near feature parity, and M1 Ultra will probably take ~1 day. We aren't starting from scratch for every new chip.
I'm not saying everyone will be happy daily driving a laptop with no GPU (I wouldn't, not as my main machine). I'm saying some people will be (I would, as a carry around laptop for browsing and SSH).
>That whole "optimized for macOS" thing is a myth. Heck, we don't even have CPU deep idle support yet and people are reporting 7-10h of battery runtime on Linux. With software rendering running a composited desktop. No GPU.
The hardware is just that good.
1. There is now a completely untapped resource on your SOC
2. Your CPU is being utilized unnecessarily for things it shouldn't have to run in the first place
3. It completely rules out any hardware-accelerated applications, which is a lot of desktop use cases
If you’ve ever used a desktop PC with an Intel CPU and a dedicated GPU, you’ve also have a completely untapped resource in your machine (unless you were rocking a Xeon or some such). It’s not entirely illogical when you consider the benefits of economies of scale.
What matters is whether the experience you can get with the hardware you do use is superior to competing offerings. Have Apple Silicon Macs reached that point for Linux users? Probably not, unless you have very specific requirements and are willing to live on the bleeding edge, but the case is starting to appear for some specific needs.
And of course, they are working on drivers for the GPU and other hardware.
What does that even mean? We have a full composited desktop with shadows and transparency and everything. Software rendering doesn't mean no OpenGL. It's just software OpenGL.
USB3 and Thunderbolt are being worked on as we speak, and USB3 already works in Sven's kernel branch.
The backlight works with the DCP display driver, which is already working but just needs to be productionized so we can ship it in our main kernel branch. Soon.
And the GPU userspace work is at 90+% GLES2 spec compliance, and the hardware interface reverse engineering to write a kernel driver (which is the simpler part) has already started.
Things are moving quickly.
You should be paid by Apple for this.
Apple pays less than $500/year to BSD developers for the millions of lines of code that they poach from them. Giving back to open source developers for doing the things they should have done in the first place isn't really "their thing" so to speak.
This is unfounded. Also Apple bought the rights to BSD before FreeBSD existed, back when it was BSD4.3 and FreeBSD would not arrive for over a decade later. Apple also hired a lot of FreeBSD's programmers (including their founder) full-time and some of Apple's technologies such as LLVM have made their way back to FreeBSD.
https://freebsdfoundation.org/our-donors/donors/?donationTyp...
> This is unfounded. Also Apple bought the rights to BSD before FreeBSD existed.
You're right. But they still poach millions of lines from FreeBSD for XNU/Darwin, since the patches are largely compatible. One would think they'd be willing to give back to the developers who write their code for them, but you'd be mistaken. Much like the App Store, it would appear that Apple is interested more in squeezing value from whoever they can and throwing them aside when they no longer make a case for their value.
"The BSD portion of the OS X kernel is derived primarily from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features."
https://developer.apple.com/library/archive/documentation/Da...
Some upstream kernel folks are already using Apple Silicon machines for development (to compile x86 kernels even) because they're faster than their x86 boxes, by a good margin :-). My M1 Pro laptop is about as fast at doing kernel builds as my 16-core Threadripper.