00:07fdobridge_: <gfxstrand> sweet!
00:07fdobridge_: <gfxstrand> Okay, docked works way better.
00:08fdobridge_: <bylaws> Oh great!
00:09fdobridge_: <bylaws> Are you looking into nvk on it or just for testing?
00:09fdobridge_: <gfxstrand> Gotta love the little glitches while docked. I'm going to guess that's X11 blitting to 4K and the GPU just not keeping up.
00:09fdobridge_: <pac85> Nvk on switch? That's exciting
00:09fdobridge_: <gfxstrand> Planning to play with NVK, yeah.
00:09fdobridge_: <gfxstrand> Right now I'm just trying to get a feel for Linux+Switch at all.
00:09fdobridge_: <pac85> Is it one of those with the vulnerable boot ROM?
00:10fdobridge_: <gfxstrand> Yeah. I bought this one about 3 months after launch so it's got all the vulnerabilities. 👿
00:10fdobridge_: <gfxstrand> Yeah. I bought this one about 3 months after launch so it's got all the vulnerabilities. 😈 (edited)
00:11fdobridge_: <pac85> Nice lol, I lost that train
00:11fdobridge_: <pac85> Nice lol, I lost that train (don't have a switch at all) (edited)
00:12HdkR: Watch out for battery expansion. Both of my launch day Switches had to get their batteries replaced over the past weeks
00:13fdobridge_: <gfxstrand> Noted
00:13fdobridge_: <bylaws> Neat, I remember trying mainline for a bit years back then gave up and ported l4t
00:14fdobridge_: <bylaws> Will be cool to have that actually be usable
00:14fdobridge_: <bylaws> Will be cool to have that actually be usable now (edited)
00:14fdobridge_: <bylaws> Will be cool to have that actually be usable in the future with nvk (edited)
00:14fdobridge_: <gfxstrand> Yeah, in theory it sorta works but there's sync problems.
00:14fdobridge_: <gfxstrand> I want to poke about at it a bit myself.
00:19fdobridge_: <gfxstrand> I would play with a different Tegra board but all I have is a Switch
00:20fdobridge_: <airlied> Kernel patches accepted :-p unless it's obviously broken, I just got rid of the two tegras I had
00:22fdobridge_: <airlied> Don't think my switch is old enough or my kids would let me touch it 🙂
00:25linkmauve: The last time I tried to upstream some Switch patches in mainline, the maintainers told me the Nvidia drivers were of very poor quality and I haven’t had the time to rewrite them yet.
00:26linkmauve: And I’m back to playing with other parts of the stack currently.
00:28linkmauve: Plus there were issues with copyright, so I kind of dropped that.
02:34fdobridge_: <gfxstrand> Well, the plan is to use stock nouveau, not whatever thing NV open-sourced.
05:58fdobridge_: <Sid> @airlied we've been trying to reach you regarding ~~your car's extended warranty~~ the job timeouts on nouveau+GSP
06:03Ellenor: I managed to get useful information just by cutting up some malformed CSV from the weather service here
06:05fdobridge_: <airlied> Yeah I might have time next week to dig in, I need to figure out if my patch to fix the locking could cause it
06:06fdobridge_: <Sid> the one that just went in/I tested a couple weeks ago? nope, not it
06:06fdobridge_: <Sid> the job timeouts occur even on mainline, unpatched
06:07fdobridge_: <airlied> Don't think it went in yet,but was going to push it, but if timeouts occur always then that is good to know,
06:09fdobridge_: <Sid> timeouts are consistent, yeah. they happen without the whole patchset, with the whole patchset, with every commit on the patchset except the 10th patch, and also with *just* the 10th patch
06:09fdobridge_: <Sid> on my setup I also saw a gsp mmu fault which @/RedSheep didn't see
06:14fdobridge_: <airlied> Is there an issue filed with reproducer info?
06:17fdobridge_: <redsheep> I don't believe either of us have filed anything, and that is correct, I have not seen the mmu fault at all. I only ever saw device lost once as well so something different about my setup makes it far far more rare, and I have no way to know that's even related to the kernel.
06:19fdobridge_: <redsheep> I am not even sure where to file one, would that be here? https://gitlab.freedesktop.org/drm/nouveau/-/issues
06:21fdobridge_: <Sid> no issue filed but I do have everything for it ready, including an apitrace that consistently timesout on nouveau+gsp but not on nouveau-gsp or on the proprietary drivers
06:21fdobridge_: <Sid> I'll file it in a while, post lunch
06:32fdobridge_: <airlied> Yeah file it there
06:38fdobridge_: <Sid> actually...
06:38fdobridge_: <Sid> this is relevant. the thread itself is a mess but it is the relevant issue
06:38fdobridge_: <Sid> https://gitlab.freedesktop.org/mesa/mesa/-/issues/10225
06:39fdobridge_: <Sid> I'll attach my files there, maybe move it to drm/nouveau? 😅
06:53fdobridge_: <redsheep> Oh yeah I forgot there was an issue I had been replying to there, I never connected that they were describing almost the exact results you have been.
07:47fdobridge_: <azkali> I put a lot of effort into resuming your work on mainline
07:47fdobridge_: <azkali> https://gitlab.azka.li/l4t-community/kernel/mainline/linux
07:47fdobridge_: <azkali> It's pretty far in completion, basically only audio stack is completely missing, other than that some small bugs exists
07:48fdobridge_: <azkali> I put a lot of effort into resuming your work on mainline
07:48fdobridge_: <azkali> https://gitlab.azka.li/l4t-community/kernel/mainline/linux
07:48fdobridge_: <azkali> It's pretty far in completion, basically only audio stack is completely missing, other than that some small bugs exists
07:48fdobridge_: <azkali>
07:48fdobridge_: <azkali> And I am currently adding Mariko support too (edited)
08:28fdobridge_: <airlied> Is that bug got the same timeout? Do I need working dxvk or do we have a reproducer without it?
08:48HdkR: Yay Mariko support
12:44shulai: Hi~Does anyone know what is GPFIFO channel? Is it different from the compute channel? Which channel does CUDA kernel commands push to?
12:49fdobridge_: <Sid> appears to be the same timeout, yes. you don't *need* dxvk but too few games run vulkan natively an the couple I have installed have it happen at random
13:46shulai:
16:00fdobridge_: <zmike.> is anyone crazy enough to look into this for me or do I gotta play gpu shuffleup on my first day back https://gitlab.freedesktop.org/mesa/mesa/-/issues/10340
16:02fdobridge_: <gfxstrand> My only instance of the proprietary driver is a Haswell box I keep tucked into the corner that isn't even plugged into a screen.
16:16fdobridge_: <zmike.> :grimace:
16:32fdobridge_: <gfxstrand> Let's Goooooo! 🏎️
16:32fdobridge_: <gfxstrand> https://cdn.discordapp.com/attachments/1034184951790305330/1191781087958007869/image.png?ex=65a6afa1&is=65943aa1&hm=8f600aac8c237475a2e8efe22262aee7d63cf2389965d4055ebbb65517357638&
16:53fdobridge_: <triang3l> But dynamic graphics state setting is not an operation on shaders 🙃
17:01fdobridge_: <pac85> Uuuhm is this doing patching of shaders?
17:01fdobridge_: <pac85> Uuuhm is this doing patching of shaders? (edited)
17:05fdobridge_: <gfxstrand> Yup. For ESO you get NULL. But I'm also planning to build a common pipeline impl on top of this and that'll provide state.
17:14fdobridge_: <!DodoNVK (she) 🇱🇹> Barbie background 🤔
17:40fdobridge_: <gfxstrand> Yup! 💖
17:42fdobridge_: <Sid> best movie I watched in 2023
18:35fdobridge_: <gfxstrand> Such a good movie. I haven't laughed and cried that hard doing a movie in, like, ever.
18:36fdobridge_: <rhed0x> I thought it was mediocre at best
18:36fdobridge_: <rhed0x> really didn't work for me
18:38fdobridge_: <rhed0x> especially the second half. The whole feminist topic is a good fit for a Barbie movie, I just wish they had any subtlety at all in how they get that message across
18:38fdobridge_: <rhed0x> I loved Oppenheimer though
18:42fdobridge_: <gfxstrand> And that's exactly why they didn't go subtle. The patriarchy isn't subtle. It's a big noisy hammer that beats people around. Meanwhile, a huge part of feminine oppression is the expectation that every time we speak up, every time we oppose a man, we have to be very subtle and hidden about it so as to not hurt male egos. So, yeah, it was a role reversal. A lack of subtlety was the point.
18:43fdobridge_: <rhed0x> fair enough, just didn't make for an enjoyable movie for me
18:43fdobridge_: <rhed0x> but I wasn't the target audience anyway and lots of people loved it, so whatever
18:44fdobridge_: <gfxstrand> That's okay. Not everyone likes every movie.
18:46fdobridge_: <rhed0x> (Just for the record, I'm not one of those "this movie hates men" idiots)
18:48fdobridge_: <triang3l> Unnormalized coordinate samplers when it's toggled in sample instructions :blobcatnotlikethis: :blobcatnotlikethis: :blobcatnotlikethis: (not on Nvidia probably, but Nvidia has 3D texture sampling with explicit gradients or something like that which is also fun)
18:51fdobridge_: <prop_energy_ball> Agree, I think the lack of subtlety kinda defeats the purpose. Things are much more impactful if you let people think for themselves and come to their own conclusion as to the message that was trying to be put across.
21:08fdobridge_: <triang3l> Will that include a magic function that runs all NIR loweings needed to get a shader you'd typically work with in a Vulkan driver? 🥵 😜
21:08fdobridge_: <triang3l> Will that include a magic function that runs all NIR lowerings needed to get a shader you'd typically work with in a Vulkan driver? 🥵 😜 (edited)
21:09fdobridge_: <triang3l> I'm at this stage when I'm looking for what specifies the `base` for vertex input loads because they are all the same 0 now…
21:10fdobridge_: <triang3l> and where that's invoked in `compiler`, `mesa` or some `amd/common` or `amd/vulkan` :blobcatnotlikethis:
21:10fdobridge_: <gfxstrand> Not quite but I'm planning to try and standardize things somewhat.
21:11fdobridge_: <triang3l> and I also have lots of comments saying where I steal from like `/* st_link_glsl_to_nir, but without linkage. */`, `/* preprocess_shader. */`, `/* st_link_glsl_to_nir. */`
21:37fdobridge_: <triang3l> oooh it's `st_nir_assign_vs_in_locations` 👀
21:37airlied: for vulkan a lot pf
21:37airlied: of drivers have a loop assigning them
21:43airlied: not near pc, and code has probably moved since i cant find it
21:49fdobridge_: <triang3l> Yeah, I see `brw_nir_lower_vs_inputs`, similar code in RADV, Lavapipe
21:51fdobridge_: <triang3l> 64-bit inputs are scary in Vulkan btw, but they are something that you really need to care about just once probably so I'll spend a few minutes/hours adding them some time later
21:53fdobridge_: <triang3l> if they're even needed really
22:37fdobridge_: <gfxstrand> They're arguably less scary in Vulkan than GL