#
✕ nick:orowith2os
#asahi-dev · 2023-04-02 14:26
orowith2oshttps://blog.tingping.se/2018/08/26/flatpak-host-extensions.html
#asahi-dev · 2023-04-02 14:26
orowith2oslet me get some more resources
#asahi-dev · 2023-04-02 14:26
orowith2osmarcan: you're thinking of the host driver, that merge request uses it for the NVIDIA driver, for example
#asahi-dev · 2023-04-02 14:25
orowith2oshttps://github.com/Frogging-Family/nvidia-all/pull/156/files
#asahi-dev · 2023-04-02 14:25
orowith2osI have something you can base it off of
#asahi-dev · 2023-04-02 14:25
orowith2osWant to give it a try?
#asahi-dev · 2023-04-02 14:25
orowith2oshmmm, maybe?
#asahi-dev · 2023-04-02 14:24
orowith2osAsahi would need to do the same to achieve something similar
#asahi-dev · 2023-04-02 14:24
orowith2osNVIDIA doesn't have an issue because it links against an older version, one that works with some of the oldest runtimes available
#asahi-dev · 2023-04-02 14:23
orowith2osmarcan: The Flatpak runtime includes a specific version of libc, in most cases older then Arch's (and alarm's). If you try to toss the native driver into Flatpak, you are going to run into glibc version errors, as well as llvm libraries and the like.
#asahi-dev · 2023-04-02 13:09
orowith2osThere's not really any other solution here :shrug:
#asahi-dev · 2023-04-02 13:09
orowith2osAll it would need to do is publish right after Mesa gets updated and it'll work just fine.
#asahi-dev · 2023-04-02 13:08
orowith2osActually, when I enabled updates for it, it updated to the latest release right away. The workflows succeeded too. https://github.com/orowith2os/mesa-asahi-flatpak/commit/71dc18316a2127cfeee36fc5848fc75d3733261c
#asahi-dev · 2023-04-02 13:04
orowith2osI've put some thought into it, and agonized quite a bit over getting it to work. I'm confident in it working just fine.
#asahi-dev · 2023-04-02 13:03
orowith2osThe Mesa package I have right now will keep in sync with the current updates, the only work that needs to be done is setting up a Flatpak repository.
#asahi-dev · 2023-04-02 13:02
orowith2osmarcan: That won't work unless you follow a model similar to NVIDIA, where you build with the oldest known used glibc version and link to *only* that.
#asahi-dev · 2023-04-02 13:01
orowith2osdottedmag: Flatpak does nothing of the sort. It just gives you the /dev device and, if you know how to communicate with it, you can do so. Everything else is handled by the kernel, including sandboxing features.
#asahi-dev · 2023-04-02 07:05
orowith2osas well as alternative arches emulation
#asahi-dev · 2023-04-02 07:05
orowith2oswhich Flatpak conveniently has full support for
#asahi-dev · 2023-04-02 07:05
orowith2osso you'd have to bundle an x86 version of Mesa
#asahi-dev · 2023-04-02 07:04
orowith2osPulling in the host drivers also presents issues, particularly when architectures come into play. For something like Asahi Linux, it has to use emulation to run Steam, but Steam can't pull in the graphics drivers *because they're made with aarch64*
#asahi-dev · 2023-04-02 07:02
orowith2osFlatpak doesn't have an issue because it provides its own *stable* drivers
#asahi-dev · 2023-04-02 07:01
orowith2osFor example, Steam brings in the drivers from the host, but that fails when the system isn't using glibc or it has to provide its own version of glibc.
#asahi-dev · 2023-04-02 07:00
orowith2osby design, Flatpak can't really bring things in from the host; that's why it bundles the NVIDIA drivers. If the OS wants to provide a more-or-less glibc-version-independent driver, it can do so easily. But otherwise, there's no guarantee on ABI stability or drivers working.
#asahi-dev · 2023-04-02 06:59
orowith2os*Flatpak, and not really.
#asahi-dev · 2023-04-02 06:16
orowith2osso syncing userspace with the kernel isn't an issue, so long as you follow Asahi Linux updates *very* closely.
#asahi-dev · 2023-04-02 06:16
orowith2osThe intent here is to *only* support the main Asahi Linux kernel and Mesa.
#asahi-dev · 2023-04-02 06:15
orowith2osI have updating set up to follow the main Asahi Linux mesa updates; if a distro uses a different update cycle, they would have to provide their own Flatpak.
#asahi-dev · 2023-04-02 06:14
orowith2oswithout them in Flatpak format, there's no GPU acceleration for *any* flatpaks.
#asahi-dev · 2023-04-02 06:14
orowith2osjannau: about your comments on https://oftc.irclog.whitequark.org/asahi-dev/2023-03-31, the intent in offering the drivers in Flatpak is so that they can be used in sync with the kernel.
#asahi-dev · 2023-03-31 04:48
orowith2osAlso, I'd appreciate it if I had some native aarch64 runners too, if a Flatpak repo is set up; aarch64 builds currently take an hour and a half to build using GitHub's runners.
#asahi-dev · 2023-03-31 04:42
orowith2osIRC is weird.
#asahi-dev · 2023-03-31 04:42
orowith2oswooooah okay, didn't mean to do that.
#asahi-dev · 2023-03-31 04:41
orowith2osClient: HexChat 2.16.1 • OS: GNOME 44 (Flatpak runtime) • CPU: AMD Ryzen 5 1600 Six-Core Processor (3.65GHz) • Memory: Physical: 30.5 GiB Total (21.2 GiB Free) Swap: 7.8 GiB Total (7.8 GiB Free) • Storage: 245.9 GB / 460.9 GB (214.9 GB Free) • VGA: Advanced Micro Devices, Inc. [AMD/ATI] Radeon R7 340 @ Advanced Micro Devices, Inc. [AMD] Family 17h • Uptime: 9h 48m 6s
#asahi-dev · 2023-03-31 04:41
orowith2osI would be pushing aarch64, x86_64, and i386 builds of the Mesa so that Flatpak can use x86 qemu emulation with GPU acceleration if desired
#asahi-dev · 2023-03-31 04:39
orowith2osappropriate package manifest is located here: https://github.com/orowith2os/mesa-asahi-flatpak/
#asahi-dev · 2023-03-31 04:38
orowith2osWould Asahi Linux be open to maintaining a Flatpak repository I can use to push to?
#asahi-dev · 2023-03-31 04:38
orowith2osHi all, I've been working on making a Flatpak for the mesa/asahi fork until it's upstreamed into Mesa and so far it seems to be in a mostly working state. The only problem now is publishing it, which I've looked into doing so via Flathub (Beta) and OBS, but neither seem to be well suited for a temporary package like this or are too hard to use.