Live data from Hacker News

Native Linux GPU Driver for Apple M1

twitter.com

251–260 of 322 posts

Re: Native Linux GPU Driver for Apple M1

#252
post #247
post #227

Earlier quoted context omitted.

And yet Linus used a MacBook Air as his daily driver for many many years. The XPS series might have caught up for a while, but until they flip over to ARM, Apple laptops simply blow anything else out of the water. What’s wrong with trying to run Linux on that?

I don’t like your implication that ARM is the only way to do this. The Apple chips are fast and low power because they are good designs built on a very modern fabrication process. It’s perfectly possible to build such chips with other designs and instruction sets, for example x86_64 or risc-v, in the same way it’s pretty common to build cheaper slower ARM processors. Plenty of folks at Intel and AMD are doing that ri…

There are fundamental issues with x86 that make it impossible to match the efficiency of ARM. Variable length instruction coding for instance, which means a surprising amount of power is dedicated to circuitry which is just to find where the instruction boundaries are for speculative execution. Made sense in the 80s when memory was scarce and execution was straightforward, but now it’s a barrier to efficiency that’s baked right into the ISA.

Re: Native Linux GPU Driver for Apple M1

#253

Earlier quoted context omitted.

I don't really understand what's the difference between AAA game and Google Chrome? I thought that modern applications heavily use GPU acceleration. Is it some subset of GPU commands that's required for desktop, compared to AAA game? Is it possible that Google Chrome will crash the OS with some tricky CSS animation (may be in the future version)?

> I don't really understand what's the difference between AAA game and Google Chrome? Hundreds of GPU features the latter doesn't use in normal hw-accelerated rendering of webpages... except maybe in doing WebGL content (and even less much fewer and older features than what AAA games want)

Right, because WebGL 2.0 is basically 2010 GPU hardware, while the upcoming WebGPU is targeting 2014 hardware.

Re: Native Linux GPU Driver for Apple M1

#254
post #13

I've been following Asahi for some time on twitter. The work she did is incredible and everything was streamed and the recordings are available in Youtube. In case you're curious about the process, here you have her YouTube profile: https://www.youtube.com/AsahiLina

cant watch, that avatars voice is just simply plain annoying. Sorry.

Re: Native Linux GPU Driver for Apple M1

#255

Earlier quoted context omitted.

I don't really understand what's the difference between AAA game and Google Chrome? I thought that modern applications heavily use GPU acceleration. Is it some subset of GPU commands that's required for desktop, compared to AAA game? Is it possible that Google Chrome will crash the OS with some tricky CSS animation (may be in the future version)?

> Is it some subset of GPU commands that's required for desktop, compared to AAA game? Yes. Compute shaders and geometry shaders are big features. Vulkan, DX12 and Metal also brought a jump in performance at the API level by allowing developers to batch commands sent to the GPU. Desktop environments can and do leverage those newer APIs to get marginally better battery life. Asahi will miss out on those benefits, but…

Yes, but WebGPU is basically the version 1.0 of the common subset of those APIs, meaning 2014 hardware.

Re: Native Linux GPU Driver for Apple M1

#256
post #247

Earlier quoted context omitted.

I don’t like your implication that ARM is the only way to do this. The Apple chips are fast and low power because they are good designs built on a very modern fabrication process. It’s perfectly possible to build such chips with other designs and instruction sets, for example x86_64 or risc-v, in the same way it’s pretty common to build cheaper slower ARM processors. Plenty of folks at Intel and AMD are doing that ri…

There are fundamental issues with x86 that make it impossible to match the efficiency of ARM. Variable length instruction coding for instance, which means a surprising amount of power is dedicated to circuitry which is just to find where the instruction boundaries are for speculative execution. Made sense in the 80s when memory was scarce and execution was straightforward, but now it’s a barrier to efficiency that’s…

Thank you very much for this interesting comment! It would be great if you would like to provide an URL with a detailed analysis of this issue.

Re: Native Linux GPU Driver for Apple M1

#257
post #132

Earlier quoted context omitted.

> I can't imagine it being enough to load many electron apps in a few years time. I honestly hopoe Electron has to improve it's performance or companies start moving off of it. It's honestly a bit of a joke at this point.

Are you all using some rare electron apps that are unknown to me because I keep hearing this meme repeated but when I look at my RAM usage[0], it never corroborates this. I just don't see how 220MB for Discord is unreasonable in any way, when Firefox with 8 tabs takes 1.2GB. Telegram written in Qt meanwhile takes 200MB, literally no difference to Discord, an electron app. [0] https://i.imgur.com/cfCRWDS.jpg

Signal is using 335MB for me right now, which feels ridiculous for a messaging app. I have Firefox running with over a thousand tabs (hard to tell how much RAM it's using with all the processes, many of which share memory, but my total system usage is around 8GB right now, so it's at least less than that), so I guess it's not scaling linearly from 8 tabs = 1.2GB. At any rate, Firefox does at least a couple orders of magnitude more things than Signal does; I think it's reasonable for it to use more RAM.

I think it's a bit weird to compare a chat app with a web browser, though, when it comes to memory usage. Maybe a better example: hexchat, a native GTK IRC client, is currently using 60MB of RAM. Telegram's native app using over 200MB is also ridiculous.

Re: Native Linux GPU Driver for Apple M1

#258
post #47

Earlier quoted context omitted.

I don't want to run a web browser to run a desktop app. I don't care how useful it is to run JS and HTML from a dev standpoint it's an absolutely absurdity that my desktop app has a CORS vulnerability.

Then you probably won't get Linux desktop support at all. Linux camp should be cheering electron.

Ah yes, let's just take those table scraps and be thankful for them...

Re: Native Linux GPU Driver for Apple M1

#259
post #77

Earlier quoted context omitted.

Quoted post unavailable.

> Also, it is not unfair to ask questions considering people are donating money for this. Anyone who is donating money to both, to discover they may be the same entity, should be rightly upset. Exactly, that's the point of a AMA (Ask Me Anything). You can literally ask them anything and as I presume you or others have paid / donated money to them and need to know what they are paying for or towards and who is doing i…

Nevermind. After looking at the VTuber videos, corroborating with the public evidence and the likely names brought out, with 99.999% certainty that the conclusion of who the VTuber is, it is indeed @marcan42 [0]

[0] https://twitter.com/marcan42

Re: Native Linux GPU Driver for Apple M1

#260
post #39

"Please temper your expectations: even with hardware documentation, an optimized Vulkan driver stack (with enough features to layer OpenGL 4.6 with Zink) requires many years of full time work. At least for now, nobody is working on this driver full time3. Reverse-engineering slows the process considerably. We won’t be playing AAA games any time soon." From https://rosenzweig.io/blog/asahi-gpu-part-6.html

Why doesn't Apple release the documentation?

Isn't there anyone inside Apple who wants to have Linux?

Isn't there anyone inside Apple who wants to help?

Post reply on HN