r/AsahiLinux • • Jun 11 '23

Priority of implementing missing or incomplete features in Asahi Linux

I wonder how the priorities for implementing different features in Asahi come to be.

I feel that there is a lot of work and buzz related to 3D graphics, and people get excited about Super Tux Kart. However, I didn't even know SuperTux Kart before reading these Asahi posts, and I feel there are many other things that should have much higher priority than optimizing the graphics engines for Super Tux Kart:

  • Loudspeaker support (so people can watch movies or do online meetings without headphones)

  • Support for external displays (so people can work on their large office screen if they are not on the go)

  • other people will have other ideas

I know that there is work going into non-3D-graphics things, and I also know ghat 3D stuff is more than just Super Tux Kart. But the priorities seem to be off in my view.

Is there something I can do to speed up things with loudspeakers or external screens? I am not a coder, but I might consider to to throw money at things

2 Upvotes

15 comments sorted by

18

u/marcan42 Jun 12 '23

The priority is making forward progress and keeping developers happy, because that's the only way the project survives. I lead the project but I don't tell people what to work on, they work on whatever they want. This isn't like a company with top-down management, that's not how open source projects work.

You seem to be quite confused as to the implications of GPU rendering improvements. The recently released OpenGL 3.1 support enables the Firefox WebRender component, which significantly increases the performance and efficiency of rendering websites, and that's just one example. I'd say that's something most users would find useful. SuperTuxKart is just one random app that can use GL 3.1, of many.

2

u/mbrennwa Jun 12 '23

I never assumed Asahi to be a top-down managed project. My main question was just how the priorities come to be so I can better understand why Asahi s not moving the way I would think would make most sense (for me and many other users).

I also did not mean to say that OpenGL 3.1 support is not useful My point was that basic things for daily "general-purpose work" like support for loudspeakers or external screens would be way more useful for almost all users.

I unerstand that many of the contributors to Asahi ate enthsiasts who simply do what they find interesting. Nothing wrong with that. However, try to take the perspective of an average user who wants to watch movies with sound coming out of the speakers, or someone who wants to do office work on his/her external screen. OpenGL3.1 is not a priority for them.

9

u/marcan42 Jun 13 '23

There are no priorities. As I said, this isn't a top-down project. That means the development work isn't an amorphous pool of available hours like it would be in a company.

There isn't even an "Asahi Linux" project as an entity. It's just a name I gave to the effort of getting stuff to work well on these machines, and therefore anyone interested in that is welcome to work with everyone else. So there is no direction, no top-down priorities. Just a website, some community spaces, and some basic community rules. As project lead I have some leeway to decide how things are integrated and will offer my opinion on priorities if someone asks me, but I'm not going to push anyone to work on any particular thing just because some people want it faster.

You could ask individual developers what their priorities are, but since most people aren't working on more than a couple things individually, that wouldn't tell you much about how time is allocated overall in the project, or what order things will be completed in.

I do step in to work on things nobody else is (like the speaker safety stuff), but my time also has to go to coordinating other things, release engineering, etc. (as well as non-Asahi stuff in my life). What I end up working on and how much time I have to spend on pure development varies wildly depending on other things that are going on, and right now a bunch of things are going on.

So really, your question just doesn't make sense for this kind of project. You may find that things aren't happening in the order you want them to, but complaining about it isn't going to change anything because that's just not how this kind of project works.

8

u/ddxtanx Jun 12 '23

Asahi Linux doesn’t exist to play super tux kart? I fear I’ve been scammed😰(/s)

2

u/Low_Effective_8907 Jun 12 '23
  1. Different people are working on different things

  2. I don't think you can change the priority of an open source project by sponsoring... Especially for talented developers they probably have their own thoughts and hate being controlled.

  3. u/cAtloVeR9998, you said that neural engine and Secure Enclave are only possible from outside contributors. But AFAIK those two are marked WIP in the progress table and the other two you mentioned are already implemented (Touch Bar mostly, might not pushed to users). I have no idea if those work come from inside Asahi or the community though :D

2

u/mbrennwa Jun 12 '23

It's not about controlling developers. It's about motivating them to get a job done that would be useful to me (and probably others).

For instance, if I'd want support for external displays, I would be happy to put down some money for someone to implement this. Any takers?

7

u/marcan42 Jun 13 '23

Sven is already working on that and the basics have been working for months. The blocker right now is making it work reliably with the Linux kernel's messy USB/switching subsystems. Sven has a full time job and does this in his spare time, so throwing money at the issue isn't going to help right now.

This isn't something you can influence by throwing money at people. FOSS bounties and such rarely work well when user-driven. Bounties started by developers work because that indicates an intent to work on something and that money would, in fact, help dedicate more time to it (or buy hardware or whatever). But if there is no bounty, sorry, that's just how it is.

Maybe your confusion is thinking nobody is working on those things you think should be prioritized? Because they are, and have been for a long time now. Stuff just takes time.

2

u/PygmyUK Jun 16 '23

You don't need Asahi to throw your money at developers. you could create your own project, put up a website offering bounty contracts to get developers to work on your priorities and look to get them pushed upstream so we can all benefit from your contribution.

Best of luck in your endeavours.

4

u/marcan42 Jun 12 '23

There is no "inside Asahi". The website has a rough list of some people involved, but like most open source projects there is no "membership" concept. People choose to work on stuff, that's pretty much it. Depending on your interpretation, you could consider Asahi "just me" (in the sense that I own the domain and most of the admin roles) or pretty much everyone working on Apple Silicon support on Linux, past and present, because why wouldn't they be part of our community?* :)

* That marketing stunt a certain company tried very early on notwithstanding. They were clearly never interested in being part of any community...

19

u/cAtloVeR9998 Jun 11 '23 edited Jun 11 '23

Different people work on different aspects of the project. Some are working on multiple areas while some are only working on a few features.

Martin Povišer has been the main one working on speakers though Hector has also been working a bunch on that front.

External display support is mainly on Sven's shoulders (though I believe there are others working on the DSP). The main holdup from what I've heard is that it is very easy to crash the subsystem so it needs to become stable before being pushed to users. Sven is working a full-time job while contributing a ton on many aspects of getting Linux working

Graphics has been a focus because that is what Alyssa and Lina want to work on. Graphics is one of the biggest items not checked off yet, and will likely not be "done" for years yet (though if all goes to plan, at least OpenGL 3.2 / Vulkan 1.0 support will be upstream by the end of the year).

Other smaller issues are being resolved mainly through contributors volunteering to fix things. Like keyboard backlight, touchbar, neural engine, secure enclave are/will be only possible through the efforts from outside contributors.

Some of the missing features are because the problems are non-trivial. For example, webcam support will take a while because the webcams are not just like any other USB/SPI camera but because of the mobile-first heritage, the image signal processor is on-die, making support a lot more complex.

Things will be ready when they are ready. It is incredible how much work has been done on a platform without OEM support.

3

u/NimrodvanHall Jun 12 '23 edited Jun 12 '23

For me it would be an ‘mps’ or ‘cuda’ implementation for tensor calculations. To be used to locally run neural nets over ‘gpu’

I recon that for the average user something like speaker implementation would be more valuable.

7

u/marcan42 Jun 12 '23 edited Jun 12 '23

Compute API frontends are completely outside the scope of the Asahi Linux project. We write the backend Mesa drivers, not the frontends. You'll have to look elsewhere for that.

We make the hardware work with the existing Linux ecosystem, and work on cross-stack improvements where they are necessary to support peculiar hardware features. GPU compute is not one of those cases, it is a largely generic thing. So please don't expect us to work on "X on Macs" when X doesn't exist anywhere else in the open Linux ecosystem and has nothing to do with Macs (proprietary nvidia drivers don't count). That's like asking us to work on a Final Cut clone.

2

u/NimrodvanHall Jun 12 '23

My apologies I was of the opinion that it was a driver ‘feature’ since ‘Cuda’ is available for Linux with arm64-sbsa.

5

u/marcan42 Jun 12 '23

CUDA is a proprietary API that is only available with proprietary Nvidia drivers on Nvidia GPUs (on supported platforms, ARM64 being one of them). It is not vendor-agnostic and not part of the open source Linux GPU stack. I think there have been various attempts to clone it but nothing really got anywhere as far as I know (yet).

Hypothetically, if GPUs do work properly on the Mac Pro (if they fixed the PCIe problem), then you could install an Nvidia card and use CUDA on it like you would on any ARM64 SBSA system. But don't expect CUDA on Apple GPUs until someone writes an open source CUDA implementation.

3

u/NimrodvanHall Jun 12 '23

Thank you for this clear and extensive answer.