#asahi-gpu · 2023-08-17 20:54
i509vcbthere was an agx opcode reference somewhere if I recall?#asahi-gpu · 2023-08-17 20:51
jannaulina: did you find an alternative solution for display/gpu testing on the m2 ultra? I finally got dcpext0/dp-altmode to work on t6020#asahi-gpu · 2023-08-17 20:28
alyssa.#asahi-gpu · 2023-08-17 20:26
alyssa(it could be written by some other compute shader, you can't read it from the cpu)#asahi-gpu · 2023-08-17 20:25
alyssano, indirect the app passes the count in gpu memory#asahi-gpu · 2023-08-17 20:24
i509vcbindirect you are told how many workgroups you have?#asahi-gpu · 2023-08-17 20:23
alyssa4. num_workgroups turns into a read from those uniform registers#asahi-gpu · 2023-08-17 20:23
alyssa3. That GPU address is mapped to uniform registers for any shader that reads num_workgroups#asahi-gpu · 2023-08-17 20:23
alyssa2. Now regardless of direct or indirect, we have a GPU address to the workgroup count in the common format#asahi-gpu · 2023-08-17 20:22
alyssa1. For direct dispatch, I upload the workgroup count to GPU memory at dispatch time.#asahi-gpu · 2023-08-17 20:22
alyssathe way I handle this in gallium is..#asahi-gpu · 2023-08-17 20:21
i509vcbalthough that might not be whats good for vulkan#asahi-gpu · 2023-08-17 20:20
i509vcbin gallium you seem to load the number of workgroups in a sideband storage?#asahi-gpu · 2023-08-17 20:17
alyssayou don't (in general) know the number of workgroups on the cpu#asahi-gpu · 2023-08-17 20:17
alyssai509vcb: the nontriviality is CmdDispatchIndirect#asahi-gpu · 2023-08-17 20:14
i509vcbHmm nvm I see something in asahi gallium#asahi-gpu · 2023-08-17 20:11
i509vcbNot sure where to look to handle nir_intrinsic_load_num_workgroups in agx_emit_intrinsic#asahi-gpu · 2023-08-17 19:49
alyssanot sure what the Right way is#asahi-gpu · 2023-08-17 19:49
alyssai509vcb: I use multi-user.target instead of graphical.target and start (sway in my case most of the time) manually from the tty on boot, so then the pkill returns the tty#asahi-gpu · 2023-08-17 19:19
i509vcbWhat's meant to be the intended way to do this?#asahi-gpu · 2023-08-17 19:18
i509vcb /s/ide/kde#asahi-gpu · 2023-08-17 19:18
i509vcbrestarting ide over ssh... I'd think just pkill -9 kwin_wayland but now am on a black screen#asahi-gpu · 2023-08-17 17:13
i509vcbWell there are other things I can do in the driver until then#asahi-gpu · 2023-08-17 17:10
alyssarebase agxv i mean#asahi-gpu · 2023-08-17 17:10
alyssawhich i was going to do next week#asahi-gpu · 2023-08-17 17:10
alyssaalthough that has uapi bumpage#asahi-gpu · 2023-08-17 17:10
alyssagpu/rust-wip branch anyway#asahi-gpu · 2023-08-17 17:07
i509vcbI was going to try to debug myself but I guess it happens with that's shipped so#asahi-gpu · 2023-08-17 17:04
alyssaI thought it's in what we ship#asahi-gpu · 2023-08-17 16:59
i509vcbalyssa do you happen to know what kernel branch the timeline stuff is implemented in?#asahi-gpu · 2023-08-17 16:54
MaryWill fix that then, thanks#asahi-gpu · 2023-08-17 16:54
alyssa3D can be up to 8192 depth#asahi-gpu · 2023-08-17 16:54
Marywe report 8192 for maxImageDimension3D so I suppose that's what we should be doing here#asahi-gpu · 2023-08-17 16:54
alyssaMary: arrays can have up to 2048 layers#asahi-gpu · 2023-08-17 16:52
i509vcb3d not so sure#asahi-gpu · 2023-08-17 16:52
i509vcb1d and 2d have a depth of 1#asahi-gpu · 2023-08-17 16:52
i509vcbhttps://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#features-extentperimagetype#asahi-gpu · 2023-08-17 16:48
MaryHmm agxv_GetPhysicalDeviceImageFormatProperties2 isn't filling maxExtent.depth, what would be an appropriate value to report?#asahi-gpu · 2023-08-17 16:26
i509vcbwhere does the timeline kernel branch live again?#asahi-gpu · 2023-08-17 16:19
i509vcblina: assuming the driver supports timeline sync objects the branch I linked last night should be in a testable state#asahi-gpu · 2023-08-17 16:08
i509vcbBack before wgpu-hal and in the gfx-hal days, there was a proper GL 4.6 backend but that never really got ported over#asahi-gpu · 2023-08-17 16:08
iyesBut anyway, this is off-topic#asahi-gpu · 2023-08-17 16:07
iyesSo 3D examples errored on the missing extension#asahi-gpu · 2023-08-17 16:07
iyesBut Bevy's 3D PBR materials use cube map arrays#asahi-gpu · 2023-08-17 16:07
iyesYep yep, Bevy works on asahi when using the GLES backend#asahi-gpu · 2023-08-17 16:06
i509vcbbut the fancy stuff will need vulkan for wgpu to expose it#asahi-gpu · 2023-08-17 16:06
i509vcbI do know that you can run wgpu in it's downlevel gles 3.0 mode currently#asahi-gpu · 2023-08-17 16:05
iyesThat's unfortunate, it was the reason why Bevy game engine's 3d rendering did not work on Asahi when I tried it.#asahi-gpu · 2023-08-17 16:05
iyesOh okay that makes sense why cube map arrays are not advertised as supported in GLES/GL