04:56orowith2os[d]: I should be getting my hands on a Shield device, so I can hopefully help out a bit when it comes in.
04:57orowith2os[d]: (should be easier for me to set that up to work on than a full desktop)
04:57orowith2os[d]: Model p2897
05:27steel01[d]: The 2019 model? The t210b01 soc isn't fully booting on mainline. I've got the first part of soc support sent to #linux-tegra, but it's not been reviewed yet.
05:28steel01[d]: https://lore.kernel.org/all/20250720-t210b01-v2-0-9cb209f1edfc@gmail.com/
05:29steel01[d]: I don't have uart set up on my 2019 unit either. Sending it out in a couple days to hopefully get that done. And once that's back, I should be able to finish the device tree for the device.
07:21orowith2os[d]: steel01[d]: Not too sure. Someone else is planning on sending it out to me.
07:21orowith2os[d]: We'll see when I get my hands on it.
07:21orowith2os[d]: I want to mainly run Linux with Waydroid for Cloudstream.
07:58phomes_[d]: mhenning[d]: do you happen to have your kernel patches for zcull in version rebased on recent kernels? I wanted to track your zcull MR in the performance sheet
08:38linkmauve: steel01[d], do you know the state of the Nintendo Shield in mainline atm?
08:39linkmauve: Two years ago I tried to upstream a few drivers, but they needed some rewrite and I was waiting for Rust to be allowed in the kernel at that time.
13:14x512[m]: gfxstrand[d]: Is it possible to use some kind of common Mesa memory pool code from NVK nvkmd code? Or reinventing the wheel is required?
13:39gfxstrand[d]: What are you needing a memory pool for? And the answer is that it's unlikely. NVKMD is intentionally pretty close to the kernel and removed from the rest of the driver.
13:42x512[m]: For semaphore memory.
13:42x512[m]: According to my tests, Mesa internally allocate and free sync object every frame.
13:43x512[m]: Allocating separate kernel memory object for each sync object is too expensive.
15:02mhenning[d]: phomes_[d]: No. I don't plan to spend any time on zcull until it's seen initial userspace review, which means I'm not currently updating the patches.
15:25chikuwad[d]: mhenning[d]: quick question re: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/36971
15:25chikuwad[d]: what happens on pre-turing cards?
15:49steel01[d]: linkmauve: There's an out of tree effort for mainline on the switch. Plan is to start pushing some of that once I finish the core part of the jetson and shield stuff. The t210 switch units boot to desktop. The t210b01 variants boot to cli userspace, but needs more work. There is a patch to get nouveau to fire up. But all of that needs a lot of cleanup before even considering patches to #linux-
15:49steel01[d]: tegra/Discord channel #Nouveau.
16:06linkmauve: Ah, they’re still using Discord, too bad I can’t get in touch then…
16:07karolherbst: well it's this channel.. I think the message was just formatting messup or the bridge doing weird things
16:08linkmauve: karolherbst, didn’t steel01[d] mean that #linux-tegra was only on Discord, and not on IRC?
16:09karolherbst: maye a different server?
16:09karolherbst: I'm not aware of any linux-tegra channel
16:15steel01[d]: Context I'm talking there is lkml.
16:15steel01[d]: The switch folk have a discord server, it's named 'Linux 4 Switch'.
16:16linkmauve: Right, that’s the issue, locking all communications behind a proprietary platform.
16:16karolherbst: ahh I see
16:16karolherbst: at least have a bridge to IRC 🙃
16:17steel01[d]: *shrugs* Yeah, I can't speak to that. My work with the switch is mainly being the 'upstream' for the android support.
16:18steel01[d]: If y'all wanted to make a channel for tegra here that's bridged to urc, those of us on the l4s server could put out some invites. I couldn't say how many would be interested in joining, though.
16:19karolherbst: the issue is I need to figure out multi channel bridging before that, it's kinda on my todo list
16:19karolherbst: but then also on my todo list is to use an open platform instead
16:19karolherbst: but it's also where the people are
16:19karolherbst: tough choices to be made
16:20steel01[d]: Yeah, I've got my issues with discords policies and such myself. But it's the primary lineage chat, so here I am.
16:21steel01[d]: Matrix gets talked about as an better alternative, but it doesn't have much market saturation afaik. Never used it myself.
16:22linkmauve: XMPP is a much, much better alternative to that, fwiw.
16:23linkmauve: It’s much more solid than Matrix in my experience.
16:23karolherbst: who knows, maybe next gen IRC will be what everybody will be using
16:23steel01[d]: I've seen guilded mentioned as well, but I know even less about that. And seems like it's focused on gaming anyways.
16:23linkmauve: I could help you setup an XMPP service alongside a web client if you’re interested.
16:24karolherbst: the issue is rather that then everybody needs to run an xmpp client additionally and then nobody is gonna do it
16:24linkmauve: I’ve been doing that for the past 17 years for myself, and nine years for various associations.
16:24steel01[d]: I want to like irc. But I don't like having to set up a relay just to get persistent messages.
16:24linkmauve: karolherbst, bridging that to IRC for people who don’t want to is also an option.
16:24karolherbst: kinda need to meet the people where they are.
16:24karolherbst: Right...
16:24linkmauve: And using XMPP for people who want the features.
16:24karolherbst: but nobody is on XMPP atm
16:25linkmauve: I am. o/
16:25karolherbst: heh
16:25linkmauve: As well as most of the people I interact with.
16:25karolherbst: the big issue with xmpp is, unless I'm mistaken, it's just plain chats, which isn't great from a community building perspective
16:25karolherbst: you kinda wnat more
16:25steel01[d]: I half tried to set up a wildfire server several years ago when hangouts to threatening to shut down. Never got much traction there either.
16:25linkmauve: What do you mean, plain chats?
16:26steel01[d]: It can do file transfer too.
16:26karolherbst: heh
16:26karolherbst: not the point tho
16:26karolherbst: I mean more like.. community stuff.. like per server custom emojis/stickers
16:26linkmauve: It has file sharing built-in, rich text formatting, voice and video chat, stickers, stuff like that.
16:26karolherbst: nr 1 feature of discord honestly
16:26linkmauve: Not custom emoji I think.
16:26karolherbst: yeah.. it's like the most important feature after being able to chat
16:26linkmauve: ^^'
16:27steel01[d]: Video/voice chat? Huh, I'm behind on the feature set.
16:27karolherbst: you might laugh at it, but it's why discord is so popular
16:27karolherbst: like every software can do chat, it's not really a "selling point"
16:27linkmauve: steel01[d], you might have encountered some XMPP clients dedicated to that, such as Zoom or Jitsi, but most desktop and mobile clients now support it as well.
16:28steel01[d]: My experience has been like 4-5 years ago. Wildfire as the server, the web ui client, and... some android client that didn't work very well. There was no good mobile client at the time.
16:30karolherbst: is push notification a thing in xmpp?
16:30steel01[d]: If the client supports it. If your familiar with hangouts before it got rebranded as 'chat', that was run on xmpp.
16:32karolherbst: mhhh
16:41linkmauve: steel01[d], Wildfire has been renamed to OpenFire in 2007, and it’s a server, so it must have been very long ago.
16:42linkmauve: karolherbst, yes, all mobile clients support it, it’s kind of mandatory on Android, and absolutely mandatory on iOS.
16:42steel01[d]: Ah shoot, yes I remember that. But old names get stuck in my head. I still call google chat 'hangouts', even though it's not even the same backend anymore.
16:42linkmauve: I recommend Conversations for Android, and Monal for iOS.
16:43steel01[d]: Like the nvidia developer forum is still 'devtalk', even though that's been... I don't know how long either.
17:00mhenning[d]: chikuwad[d]: currently no change for pre-turing, which is to say the gallium nvc0 driver is still the default
17:28gfxstrand[d]: x512[m]: Yeah, for shared semaphores, we need to alloc one per sync. For internal, we want a reuse pool. You also don't want to burn a whole 4k for each internal semaphore.
17:29HdkR: Just think if you had 64kb page sizes. One page per semaphore? :D
17:31gfxstrand[d]: :frog_upside_down:
17:33karolherbst[d]: I wonder if cache lines matter
17:33karolherbst[d]: they are atomic operations after all
17:35HdkR: Don't they always matter for false sharing unless remote atomics end up being used?
17:39chikuwad[d]: mhenning[d]: okie awesome, thanks c:
19:01jja2000[d]: steel01[d]: is there another chat than #tegra? That one is kinda dead.
19:02steel01[d]: jja2000[d]: On what server?
19:03jja2000[d]: Oh nvm, that's an old chat... hmmm
19:04steel01[d]: The vast majority of my discussions are on the Lineage server on maintainer only channels. There's some talk about stuff on the l4s server, but not a whole lot going on there atm.
19:04jja2000[d]: I'd love to try and get nouveau working a bit better on the pixel since it's... not
19:05jja2000[d]: And you mentioned some patches that would help getting it to work a bit mor stabily
19:05jja2000[d]: Not for Android in this case, but that may not be an impossibility in the future
19:05steel01[d]: Afaik, there's not a lot of interest in tegra on mainline. There's me pushing stuff. And clamour now. d.ivo is doing some stuff for the pixel c. And it's all disparate, afaik there's no good unified place for discussions.
19:06jja2000[d]: Hmm bummer
19:07jja2000[d]: clamor is more focussed on older SoC's and has no interest in 64-bit stuff (he has 1 k1 device, but that's it)
19:07steel01[d]: Dmitry got busy with stuff, from what I hear. So not much moving for grate.
19:08jja2000[d]: I've thought about suggesting l4s people to make a more common server/channel since the gitlab is already called `l4t-community` anyway
19:08steel01[d]: I'd like to support t114 and t124. But for t124, I can't even get nouveau to fire up on the android bootloader. And t114 is kind of the red headed step-child. Not many people wanting to touch it.
19:08jja2000[d]: Has no nouveau either :p
19:09steel01[d]: It's the previous gpu arch, not compatible with nouveau.
19:09jja2000[d]: What T124 device do you have? You could ask Clamor for help to get u-boot on there.
19:09steel01[d]: Jetson tk1, ardbeg, shield tablet, and some other protos. I've got a bunch.
19:09steel01[d]: Oh, I've got mocha too. The one he worked on.
19:09jja2000[d]: Yeah that one should work up to some level
19:10steel01[d]: But last I talked to him: a) he didn't care about Linux itself and hadn't pushed his mocha dt. And b) hadn't even looked at nouveau at all.
19:10steel01[d]: I did get some help from him to get get u-boot chainload going on t124. It didn't want to play at first.
19:14steel01[d]: https://github.com/u-boot/u-boot/commit/df3443dfa449ad02bef8ddf6e2c90a6fd9394fc9
19:14steel01[d]: I am guessing my k1 woes are related to this, but I'm not entirely certain. When u-boot is run in non-secure mode as a chainload, it can't run stuff like that. But even when I pulled in the tlk driver and sent a vpr config command, nouveau still hangs the kernel the first time it tries to access a register. And yes, I verified that tlk smc commands were getting handled properly.
20:56hentai: Where do I put this? https://paste.c-net.org/QuirkyCaesar
20:58mhenning[d]: File a mesa issue https://gitlab.freedesktop.org/mesa/mesa/-/issues
21:02mhenning[d]: Is anyone willing to test a kernel fix on a maxwell card? I don't have the hardware to test maxwell. https://gitlab.freedesktop.org/mhenning/linux/-/commit/b3ef72898ae2bf19cf587b8679d193c9570ddb05
23:45gfxstrand[d]: Ah, good ol RT linear mismatch...
23:49gfxstrand[d]: mhenning[d]: Yeah, I wondered about that. I don't even know if those cards run fast enough to trigger it. 🙃
23:50gfxstrand[d]: But if it doesn't blow up, it's probably a good idea.