00:00mohamexiety[d]: Would be fine with that, it sounds like a good idea. As for time zones honestly I don’t mind, I got used to adjusting so I am flexible in this regard
00:01phomes_[d]: I think that it would be a good thing to do
00:07phomes_[d]: I coach football on Tuesdays from 16-18 and Thursdays from 17-19. CET. Other than that I am flexible with times
00:26Jasper[m]: alright, took a little while, but now I actually have some useful logs for when sddm is not showing with Nouveau enabled on Tegra X1: https://paste.centos.org/view/c5afdf2c
00:27Jasper[m]: (loglevel is slightly higher than normal because normally you either can't see anything or it just gets spammed with invalid operation lines)
00:27Jasper[m]: I see kernel logs are cut off
00:31Jasper[m]: https://paste.centos.org/view/6af385d8, this is the full one
00:56dwlsalmeida[d]: gfxstrand[d]: Sounds nice
03:19tiredchiku[d]: I'd also like to join in if possible :)
03:36orowith2os[d]: I'll listen in if I'm available, seems fun to listen to y'all's progress
11:30karolherbst[d]: I wonder if I should, because I'll just feel depressed not being able to do 1000 hours of coding within a day
11:31Jasper[m]: @_oftc_karolherbst[d]:matrix.org 25x developer
11:31Jasper[m]: s/25x/125x/
11:33karolherbst: Jasper[m]: you might want to file a bug against your matrix bridge, because it doesn't seem to properly replace @s to the IRC nick: "@_oftc_karolherbst[d]:matrix.org 25x developer". It's not a big deal, just mostly curious if it's a known thing
11:34Jasper[m]: It's the regular matrix.org one, but I'll keep it in mind.
11:35Jasper[m]: Does it show weirdly on IRC aswell or just discord?
11:37karolherbst: also on IRC
11:38karolherbst: the discord bridge would translate it into a proper ping and such, but can't if it has the matrix layout
11:38Jasper[m]: @karolherbst does this one work properly?
11:39karolherbst: yes
11:39karolherbst: I wonder if it's the [d] suffix it gets confused about...
11:39karolherbst: or did you change anything?
11:40Jasper[m]: Nope, just mentioned the IRC native nick not the one with the square brackets
11:40karolherbst: mhhhh
11:40karolherbst: yeah so I guess it might not like the [d] part
11:40Jasper[m]: I'll see if I can find the right place to file a bug
11:40karolherbst: let's see...
11:40karolherbst[i]: try pinging me now
11:42Jasper[m]: @_oftc_karolherbst[i]:matrix.org elo
11:42karolherbst[i]: yeah...
11:43Jasper[m]: Broken?
11:43karolherbst: so yeah.. it seems it's the brackets
11:43karolherbst: "@_oftc_karolherbst[i]:matrix.org elo"
11:45Jasper[m]: Alright, I'll try to file a bug somewhere
11:45karolherbst: cool
11:46Jasper[m]: Meanwhile, I was pointed in the direction of a collection of reverts that would supposedly improve things on TX1. Haven't tested them yet, but will soon. https://build.opensuse.org/package/show/home:Azkali:Tegra:Icosa_testing/mesa-nvk
11:46Jasper[m]: Originally made to mess around with for the switch
11:48karolherbst: yeah, any help there is welcomed
11:48karolherbst: might even be cool if one could properly maintain and wire up CI systems for continuous testing there
11:48karolherbst: we kinda have some of it, but more would be better
11:53Jasper[m]: karolherbst, do you have some resources for that? I have a pixel c and a jetson tx2 available
11:53karolherbst: https://docs.mesa3d.org/ci/index.html
11:56Jasper[m]: I'll check it out, will have to see up to what point it needs to function though. Can imagine that'll be semi-annoying with these
11:57Jasper[m]: Getting more devboards might be a better approach to that though.
12:01karolherbst: yeah.... the most important part would be for the system to be reliable, because we actually use the CI farm in pre-merge testing
12:01karolherbst: so it also would need somebody to actively maintain it
12:06Jasper[m]: We'll see, should normally be doable as long as the base OS can be recovered/approached somehow
12:12Jasper[m]: Gonna be harder on the pixel c since uart doesn't seem to be interactive. The jetson's will do fine for that probably
21:27zmike[d]: next week I'm planning a nvk+zink bug rodeo, so if anyone's got unfiled bugs make sure you get em filed
21:48gfxstrand[d]: https://tenor.com/view/rodeo-yellowstone-cowboy-yeehaw-holding-on-gif-17723197
21:48gfxstrand[d]: zmike[d]: trying to fix bugs ^^
21:53orowith2os[d]: oh, on that note, can someone on NVK test with Zink and Firefox to see if it has graphical glitches?
21:53orowith2os[d]: need to see if this is just an AMD-specific thing ^^
21:53orowith2os[d]: basically the entire right half of the window goes wonky
21:54ermine1716[d]: orowith2os[d]: Not nvk, but got the same thing on anv, so it's not amd-specific
21:55orowith2os[d]: good enough for me
21:55orowith2os[d]: I'll see if I can find a zink bug and file it if not
21:55orowith2os[d]: and move over to Discord channel #zink🔗