01:01 karolherbst: might be some firmware problem
01:05 fodasso: I think I have them all installed...
01:05 fodasso: They might be not loading properly with inbuilt modules, perhaps?
01:06 karolherbst: ahh yes.. don't use builtin modules with drivers requiring firmware
01:06 karolherbst: or make sure you include all the files you need
01:06 karolherbst: anyway, dmesg should tell
01:07 fodasso: ok, tyvm. Will try rebooting to try to fix that up and will get that dmesg output. see ya :)
03:29 fodasso: It was indeed the firmware, which was not installed properly. Now I installed the files, checked which ones were loaded and built them all to the kernel
03:30 fdobridge: <a​irlied> been trying to solve dEQP-VK.renderpass.suballocation.attachment_write_mask.attachment_count_2.start_index_1 but something in the fragment shader output routing is escaping me
03:30 fodasso: This way I bloat up the kernel, but limit what files could be loaded as firmware from userspace...
03:30 fodasso: Next thing I will try NVK properly. tyvm once again
06:34 fdobridge: <a​irlied> @gfxstrand once I dump shaders with the dump layer, what do I do with the output files?
06:40 fdobridge: <g​fxstrand> Oh, I have a better tool for shaders
06:41 fdobridge: <g​fxstrand> https://gitlab.freedesktop.org/gfxstrand/nvdump
06:41 fdobridge: <g​fxstrand> IDK that it works with all the stages yet, though. My attempts at decoding their binary headers are still really sketch.
06:42 fdobridge: <g​fxstrand> That little bit of rust takes a spv file (binary) and runs it through their driver with `VK_EXT_shader_binary` and disassembles the binary.
06:42 fdobridge: <g​fxstrand> When it works it's amazing.
07:14 fdobridge: <a​irlied> oh I might be able to leverage that,
07:40 fdobridge: <a​irlied> ah found it without shaders. https://gitlab.freedesktop.org/nouveau/mesa/-/merge_requests/247
07:51 fdobridge: <a​irlied> that only took 2 or 3 days to dig up, flu sucks 😛
08:04 fdobridge: <a​irlied> @karolherbst @gfxstrand just noticed LOAD_ROOT_TABLE/SET_ROOT_TABLE_SELECTOR in some traces on turing, is it a new way to launch shaders or bind things?
08:27 fdobridge: <a​irlied> also dEQP-VK.binding_model.shader_access.primary_cmd_buf.uniform_buffer.geometry.descriptor_array.offset_view_nonzero passes with NV50_PROG_OPTIMIZE=0 or 1
08:27 fdobridge: <a​irlied> if anyone is feeling codegen
08:37 fdobridge: <a​irlied> AlgebraicOpt:LOGOP
09:18 fdobridge: <k​arolherbst🐧🦀> yeah, turing was a big rework on a couple of things
09:20 fdobridge: <k​arolherbst🐧🦀> mhhhhh... mind sharing the diff between that enabled/disabled?
10:05 fdobridge: <a​irlied> uggh coloriser
10:05 fdobridge: <a​irlied> https://paste.centos.org/view/raw/d8524a4b
10:06 fdobridge: <a​irlied> https://paste.centos.org/view/raw/71b4b2c9 non-color
10:22 fdobridge: <k​arolherbst🐧🦀> @airlied nvk should add a `info->omitLineNum = debug_get_num_option("NV50_PROG_DEBUG_OMIT_LINENUM", 0);` thing 😄
10:23 fdobridge: <k​arolherbst🐧🦀> makes diffing way better
10:25 fdobridge: <k​arolherbst🐧🦀> mhhhh
10:27 fdobridge: <k​arolherbst🐧🦀> I wonder if that `OP_LOP3_LUT` stuff messes up things
10:28 fdobridge: <k​arolherbst🐧🦀> @airlied mind dumping the shader right after AlgebraicOpt and with omitLineNum set?
10:29 fdobridge: <k​arolherbst🐧🦀> `this->print();` should do it
10:30 fdobridge: <a​irlied> Will be tomorrow, powered down for night
10:30 fdobridge: <k​arolherbst🐧🦀> okay
13:44 fdobridge: <g​fxstrand> @karolherbst Any thoughts about https://gitlab.freedesktop.org/nouveau/mesa/-/merge_requests/248 before I pull it in?
13:45 fdobridge: <g​fxstrand> In particular, any thoughts around how I'm handling the handful of depricated APIs we're using. I wanted to keep nouveau_drm.h an exact copy of the kernel header if possible.
13:54 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> "depricated"
13:58 #dri-devel: < KungFuJes14:16 fdobridge: <k​arolherbst🐧🦀> yeah.. I don't know if userspace can even use it
14:16 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> You can resolve this thread now: https://gitlab.freedesktop.org/nouveau/mesa/-/merge_requests/248#note_2022419
14:16 fdobridge: <k​arolherbst🐧🦀> anyway... my bet was on "new UAPI" so I didn't really bothered as much
14:17 fdobridge: <k​arolherbst🐧🦀> I think the idea was to use nvif for everything, but...
14:17 fdobridge: <k​arolherbst🐧🦀> all that stuff is a bit weird
14:17 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> I remember there being a MR for Wine which fixed quite a few typos 🍷
14:18 fdobridge: <g​fxstrand> Where does nvif come from? Is it a kernel-defined thing or something that's actually in hardware?
14:18 fdobridge: <k​arolherbst🐧🦀> kernel defined
14:18 fdobridge: <g​fxstrand> Then it needs to be in `src/include/uapi/`
14:18 fdobridge: <k​arolherbst🐧🦀> well.. it's not
14:18 fdobridge: <g​fxstrand> Yeah, I can see that
14:19 fdobridge: <k​arolherbst🐧🦀> I think the best bet is on making it all proper with the new UAPI and move things over so we can just cut it all of or something...
14:22 fdobridge: <g​fxstrand> This whole think feels like a case study in why we have open-source userspace requirements for new kernel API...
14:23 fdobridge: <g​fxstrand> In any case, I think I'm going to go ahead with that MR. It doesn't make anything worse (now that I've fixed the typos) and it makes it easier to pull in the updated headers.
14:23 fdobridge: <k​arolherbst🐧🦀> yeah
14:24 fdobridge: <k​arolherbst🐧🦀> might as well pull in all the other headers... but...
14:29 fdobridge: <k​arolherbst🐧🦀> maybe we want to require that NVK only uses things from `src/include/uapi/` and clean that entire mess up
14:30 fdobridge: <g​fxstrand> Yes, I would like that.
14:30 fdobridge: <g​fxstrand> IDK that I want to make it a requirement for merging NVK because APIs do exist even if they're badly documented and in the wrong spot but that should be the end goal.
14:31 fdobridge: <k​arolherbst🐧🦀> ahh yeah.. maybe "unless it's used by GL" is a fair exception