Bullshit.
Intel and AMD both contribute to the Linux kernel to have their hardware, CPUs and GPUs both, supported.
Show me Apple's commits for supporting the M1 within the kernel and we'll talk.
Until then, in this situation where you're trying to get Asahi Linux running for the M1, it is not exactly the same.
Support from chip manufacturers doesn't mean you're actually going to end up with a better user experience.
Odd, because here I am with an Intel laptop running Linux that manages that just fine.
> Support from chip manufacturers doesn't mean you're actually going to end up with a better user experience.
Honestly, this is just ridiculous. Go ask the Nouveau folks how their reverse engineering project is going.
I love the drive you guys have, and I wish you the best of luck. But Apple could pull the rug out from under you any time they want in a future hardware rev (either deliberately or accidentally), and all you can do is keep on reverse engineering in the hopes of keeping up.
Edit: Updated pronouns since apparently the OP is one of the project maintainers.
Then it's not an Ivy Bridge running multiple external displays on KDE.
> Honestly, this is just ridiculous. Go ask the Nouveau folks how their reverse engineering project is going.
Nvidia created an actively hostile firmware situation. We already have the firmware story worked out. Plus having to support a bazillion GPU generations with incompatible interfaces burns people out. We're starting with one, and Apple has a much better track record of incremental change and avoiding hardware churn. This is unique, and we've literally heard from Apple employees that this is an explicit goal. It shows all throughout the SoC design.
> and all you can do is keep on reverse engineering in the hopes of keeping up.
And we will keep on reverse engineering, and we'll keep up :-)
Tiger Lake (whose microarchitecture I just learned is Willow Cove) running Gnome via Wayland (damn HiDPI...), single external display via USB C dock plus an onboard.
More fully, previously I was running a Lenovo X1C5 with Intel integrated graphics. Again, no issues there. In that case I ran Xorg with TearFree enabled.
I'm currently running a Framework sporting an i7-1165G7 with the aforementioned setup.
It was genuinely a little shocking, having spent my earlier days manually hacking modelines in X, to see this hardware come up flawlessly on first boot with Ubuntu 21.04... amazing what a reasonably open hardware ecosystem will enable. jab jab ;)
> We're starting with one, and Apple has a much better track record of incremental change and avoiding hardware churn. This is unique, and we've literally heard from Apple employees that this is an explicit goal. It shows all throughout the SoC design.
Absolutely a fair point! I concede that the reverse engineering story with Apple may very well be less painful than it is with other vendors. Honestly, I hope for your sanity that it is! :D
The statement they made is ridiculous, and I stand by my decision to label it as such.
If you want to explain to me how I'm wrong instead of simply appealing to authority, you're obviously free to do so.
That sounds entirely ridiculous and unsupportable to me.
And please don't trot out the "appealing to authority" bit. That absolutely doesn't apply here; when it comes to an opinion about some hardware/software project, I would 100% take the word of the lead developer on that project over a rando on HN who has for some inexplicable reason decided to pick a fight about something they appear to not have any domain knowledge about.