02:23imirkin: pendingchaos: didn't you have a series to use SULDP everywhere, and implement the GL ext for not having to specify the read format?
02:55karolherbst: imirkin: btw, any preference on gitlab vs mailing list? I think it would be easier to keep track of patches not merged yet than with patchwork and I could start putting all my more or less finished things as MRs on gitlab
02:56imirkin: might be easier to keep track (questionable), but certainly makes it less likely to get reviewed
02:57imirkin: i'm good at checking email, reading it, replying. gitlab's yet-another thing to log into and check
02:57imirkin: and forget about
02:58imirkin: the fact remains that the author of the patch has to want to get it in, in order for the patches to get the necessary attention
02:58imirkin: whether they're no a mailing list, patchwork, gitlab, or where-ever
02:58imirkin: on a*
03:07imirkin: but ... i doubt anyone cares about my opinion, given that it's definitely happening
03:07imirkin: and for people who're working on this stuff full time, perhaps it does make more sense
03:08imirkin: which is the majority of the mesa contribution base
05:05HdkR: imirkin: Oh, you thinking about getting shader_image_load_formatted supported?
05:05imirkin: i'm sure pendingchaos sent patches
05:07HdkR: Nice :D
05:07imirkin: mareko had some minor comments on the first one
05:08imirkin: pendingchaos: any interest in picking that up again?
05:09HdkR: Hoping Intel picks it up on Gen 11+ or w/e it is to have it without hardware bugs :)
16:13stoatwblr: hi guys, what's support like for K1+K2+K20 in the same box?
16:13stoatwblr: as in "for opencl purposes"
16:16stoatwblr: and yes, I know that's an oddball setup to have in one box.
16:18karolherbst: stoatwblr: nouveau doesn't support any compute API out of the box
16:18karolherbst: but technically you could use them for compute without any issues, it just might be a little slow
16:18stoatwblr: I noted it's tagged WIP
16:19karolherbst: well I don't expect CL 1.2 to be supported in the next 5 years
16:19karolherbst: except somebody else taks over after I am done with adding the general support for CL
16:19karolherbst: and that's moving quite slowly
16:20stoatwblr: would access to the devices assist?
16:21karolherbst: I usually have access to various kind of hardware to test things. That's not the issue
16:21karolherbst: it's more of a lack of developers kind of thing and more pressing issues
16:21stoatwblr: I know that feeling
16:25karolherbst: I hope that I am getting everything merged for getting CL 1.1 running (or at least what clover supports), but even support for images is questionable as it depends on various things
16:29karolherbst: imirkin: I ran the GLES3 CTS and I think we might have new fails (or there are old, dunno): https://gist.githubusercontent.com/karolherbst/646e813e8fea0bad9b9abcf813082655/raw/0ed1486e78345fd662f0413d2b6a01c6bc67259b/gistfile1.txt
16:29karolherbst: know anything about those?
16:29karolherbst: the 5 first I know what those are about
16:29karolherbst: I assume that those copy_tex_image_conversions tests are just new
16:30karolherbst: hum "[GL_RGBA4]=>[GL_RGBA32UI] conversion [src target=GL_TEXTURE_2D, dst target=GL_TEXTURE_2D] caused  error instead of GL_INVALID_OPERATION."
16:30karolherbst: passes on intel though
17:03karolherbst: ohh those are RGBA4 -> something conversions... meh
17:55karolherbst: imirkin: mhhh, the CTS indeed hardcodes RGBA4 to be renderable :/
19:03pendingchaos: imirkin: I think what's left for the series is to rebase, finish the 1st patch and for the 4th and 5th patches to be reviewed
19:03pendingchaos: so I think I'll do the first two sometime
19:03pendingchaos: I don't have my 1060 plugged in, so I can't easily test it
19:03pendingchaos: but I think it should be fine, afaik nothing changed in a way that could break the series
19:06karolherbst: imirkin: okay, so GL_RGBA4 is required to be color renderable for GLES
19:06karolherbst: so I guess we more or less have to disable RGBA4 at least for GLES
19:51karolherbst: ahhhh disabling RGBA4 leads to even more fails :/
19:58imirkin_: yeah, i'm getting a bit sick of fighting the RGBA4 fight
19:58imirkin_: i'm pretty sure i'm right
19:58imirkin_: but ... everyone else is writing conformance tests that say i'm wrong
19:59karolherbst: imirkin_: I think for GLES the situation is clear
19:59imirkin_: "color renderable" doesn't necessarily mean what you want it to mean
19:59imirkin_: it means "is a valid enum to be passed in in certain places"
19:59imirkin_: but i'm fairly sure you can decline to render to an attached texture for any reason at all
19:59imirkin_: including phase of the moon
19:59karolherbst: okay so rendering into a texture might be enough to satisfy this
20:00karolherbst: but now with disabling it, it gets even more annoying
20:00karolherbst: the CTS tries to copy RGBA4 into RGBA8
20:00karolherbst: and expect this to fail
20:00karolherbst: because bit size changes
20:00karolherbst: but... we fall back to RGBA8 because RGBA4 isn't supported
20:00imirkin_: that would fail on radeonsi too
20:00karolherbst: so we do the copy
20:00karolherbst: appearantly the test is happy with intel
20:00karolherbst: didn't test radeonsi
20:01imirkin_: they probably expose RGBA4 =]
20:01karolherbst: ohh, probably
20:01imirkin_: and they don't use the st/mesa code
20:02imirkin_: [unless you were testing iris]
20:02karolherbst: imirkin_: btw, I saw those black rectangles running nouveau in chromium here
20:02imirkin_: what gpu?
20:03imirkin_: is that with the uniform whatever fixes?
20:03karolherbst: currently on 2b876bc922
20:03karolherbst: mhh let me check
20:03imirkin_: which is newer than several months ago?
20:04karolherbst: yeah, from this month
20:04imirkin_: i wonder if we should just ask distros to not include nouveau_dri by default
20:04karolherbst: that would be harsh
20:04imirkin_: lots of people have lots of hard-to-debug problems
20:05imirkin_: and aren't explicitly choosing to use nouveau
20:05imirkin_: if you then install nouveau, then fine
20:05karolherbst: right, but those weren't as bad if we wouldn't cause X to freeze eg
20:05karolherbst: just because some channel got messsed up
20:05imirkin_: but many times they do
20:05karolherbst: that's what annoys me the most right now
20:05karolherbst: was playing some game, channel broken -> X froze to death, no way to get into the tty
20:06karolherbst: killing the application -> X unfreezes
20:06karolherbst: that's just a super stupid situation
20:06karolherbst: maybe we should just sigkill the application from nouveau ...
20:07karolherbst: I was able to have an event listener thing set up to handle that within mesa, but it doesn't work if the same application listens to vsync events as it's basically the same thing :(
20:07karolherbst: so, no glamor or wayland compositors
20:08karolherbst: skeggsb told me/us that the command submission rework would fix that as we would get notified about this through the API, but....
20:09karolherbst: this just sound like stupid issues we should be able to solve in no time
20:09imirkin_: i guess you'll be sending a patch shortly then :p
20:09karolherbst: thing is, skeggsb already wrote those
20:09karolherbst: he just doesn't publish them as those changes are important for vulkan as well
20:09karolherbst: and he wants to mockup those while working on a vulkan driver
20:10karolherbst: and I just don't want to spend time writing patches and get told later "huh, I already have something like that"
20:15karolherbst: *sigh*, I guess I could do event dispatching within libdrm to solve that vsync event issue. let's see how painful that would be
21:14karolherbst: imirkin_: okay, maybe you know of a simple fix to solve that. Currently I do a poll of the nouveau_drm.fd to get whatever event the kernel module wants to pass me in. Thing is, for the vblanks we more or less do the same, but on a different fd. Now I have the issue that both events arrive at both fds used :/ any ideas?
21:15karolherbst: the fd is created via a fcntl(fd, F_DUPFD_CLOEXEC, 3); of the fd passed into nouveau_drm_screen_create
21:52pmoreau: karolherbst: I just saw you updated a couple of branches; I should be looking at “nouveau_nir_v9” for reviewing the final patches and running “nouveau_nir_spirv_opencl_hmm_v3” if I want to test it out, right?
21:57karolherbst: nouveau_nir_spirv_opencl_hmm_v2 if you want to test it out
21:58karolherbst: v3 needs some major rework I think
21:58karolherbst: it works, but not that well
22:00karolherbst: pmoreau: and “nouveau_nir_v9” for reviewing nir is correct