#asahi-gpu · 2023-08-16 08:42
iyesYea ofc, for someone unfamiliar with the codebase, need easier things to get into the flow of things. :)#asahi-gpu · 2023-08-16 08:41
jannaufoccus is slowly shifting but I think the main missing features for opengl (es) are not good first task#asahi-gpu · 2023-08-16 08:39
jannauthe "good-first-task" labelled one in https://gitlab.freedesktop.org/mesa/mesa/-/issues/?sort=created_date&state=opened&label_name%5B%5D=asahi&first_page_size=20 maybe#asahi-gpu · 2023-08-16 08:39
jannaualyssa might have other start task#asahi-gpu · 2023-08-16 08:38
iyesOh so the dev efforts are currently focused on Vulkan and not GL?#asahi-gpu · 2023-08-16 08:38
iyesYea I think I'd rather try my hand at mesa userspace stuff, even though it is in C, because of the simpler dev workflow.#asahi-gpu · 2023-08-16 08:37
jannauI think a good starting task atm might be fixing easy failing test cases from the vulkan cts in https://gitlab.freedesktop.org/asahi/mesa/-/tree/agxv/main#asahi-gpu · 2023-08-16 08:35
jannau`meson devenv` sets the environment up to test drivers from the dev tree#asahi-gpu · 2023-08-16 08:34
jannauthe mesa driver OpenGL and vulkan drivers (C) can be tested on the development system#asahi-gpu · 2023-08-16 08:33
jannauiyes: fast iterating on the rust kernel driver works with a development + test machine using m1n1's lightweight hypervisor#asahi-gpu · 2023-08-16 08:29
iyesAlso, out of curiosity, has the needed RE work to support cubemap array textures been done? Or is that still blocked on unknowns about the hardware?#asahi-gpu · 2023-08-16 07:50
iyesHow does one iterate on a gpu driver? How can I easily test changes? Also, where can I find documentation?#asahi-gpu · 2023-08-16 07:48
iyesI have an Asahi (the ALARM based, not Fedora based) install on a M1 Pro MBP, which I don't daily drive but occasionally dual boot into. I don't mind trashing / littering over that OS install. Any advice for how I should set up my workflow for mesa dev?#asahi-gpu · 2023-08-16 07:46
iyesHello. :) I'd like to try to contribute. I have a decent understanding of graphics APIs (from a user POV, not an implementer POV), hardware (though more CPUs than GPUs), and I am good at Rust and C (though my C is ... rusty ;) ). Never worked on a gpu driver before.#asahi-gpu · 2023-08-16 01:34
alyssawomp#asahi-gpu · 2023-08-16 01:23
i509vcbnothing of value will be lost at least#asahi-gpu · 2023-08-16 01:13
i509vcbpulls out 2nd laptop #asahi-gpu · 2023-08-16 01:09
i509vcbBut did not enable the swapfile yet#asahi-gpu · 2023-08-16 01:09
i509vcbI *might* have accidentally ran mkfs.swap on RecoveryOSContainer#asahi-gpu · 2023-08-16 01:07
i509vcbI think I fucked up a lot harder#asahi-gpu · 2023-08-16 01:07
i509vcbnever mind the missing swapfile#asahi-gpu · 2023-08-16 01:05
cr1901"It was at this moment i5 knew he fucked up"#asahi-gpu · 2023-08-16 00:58
i509vcbnarrator: in a moment of stupidity i5 realizes his swapfile isn't even setup#asahi-gpu · 2023-08-16 00:54
i509vcbshould I be getting stuff oom killed running dEQP-VK.memory.*?#asahi-gpu · 2023-08-15 21:27
alyssa(setting it and running the deqps would be the way to find out..!)#asahi-gpu · 2023-08-15 21:27
alyssaI don't think it's tested, though I'm under the impression it "should" work#asahi-gpu · 2023-08-15 21:05
i509vcbagxv currently unsets VK_SYNC_FEATURE_TIMELINE, I'm guessing the kernel driver work for timeline semaphores is not yet done?#asahi-gpu · 2023-08-15 20:22
alyssa\o/#asahi-gpu · 2023-08-15 19:36
i509vcbI've gotten api.external.memory.* to pass#asahi-gpu · 2023-08-15 19:36
i509vcbalyssa: expect VK_EXT_external_memory_dma_buf soon in agxv, just a bunch of other stuff I need to implement from dependent extensions.#asahi-gpu · 2023-08-15 14:12
alyssa:+1:#asahi-gpu · 2023-08-15 14:12
i509vcbif page size is an issue we can always just have another patch#asahi-gpu · 2023-08-15 14:12
alyssaProbably the SHA1 you listed above is good then#asahi-gpu · 2023-08-15 14:11
i509vcbHence the question around vm_page_size#asahi-gpu · 2023-08-15 14:10
i509vcbGL_EXT_external_objects is less specific but it should match vulkan#asahi-gpu · 2023-08-15 14:08
i509vcb> deviceUUID must be immutable for a given device across instances, processes, driver APIs, driver versions, and system reboots.#asahi-gpu · 2023-08-15 14:08
i509vcbThe vk spec states#asahi-gpu · 2023-08-15 14:07
alyssaalthough I think vm_page_size you're referring to is the GPU page size...? which would always be 16K?#asahi-gpu · 2023-08-15 14:06
alyssaI "dual-boot" 4K and 16K kernels on my MacBook#asahi-gpu · 2023-08-15 14:06
alyssaCorrect, but it is totally legitimate to swap out the kernel and reuse the userspace#asahi-gpu · 2023-08-15 14:06
alyssa13:46 i509vcb | Last I recall Linux can't really do dynamic, per process page sizes#asahi-gpu · 2023-08-15 14:06
alyssaShrug#asahi-gpu · 2023-08-15 14:06
alyssa13:45 i509vcb | alyssa: do we want to consider the vm_page_size in the uuid as well?#asahi-gpu · 2023-08-15 13:49
i509vcbOn that topic what is vm_page_size supposed to be?#asahi-gpu · 2023-08-15 13:46
i509vcbAlso I decided to throw the abi version in the hash for good measure#asahi-gpu · 2023-08-15 13:46
i509vcbLast I recall Linux can't really do dynamic, per process page sizes#asahi-gpu · 2023-08-15 13:45
i509vcbalyssa: do we want to consider the vm_page_size in the uuid as well? #asahi-gpu · 2023-08-15 13:32
alyssaand better safe than copyright infringing ;)#asahi-gpu · 2023-08-15 13:32
alyssaseems good#asahi-gpu · 2023-08-15 05:07
i509vcbSHA1("agx" + gpu_generation + gpu_variant + gpu_revision) if you were wondering