03:23 nmschulte: ;q
03:23 nmschulte: :blush:
06:49 MrCooper: KungFuJesus: Mesa dropped DRI1 drivers for the 8.0 release, over 10 years ago
07:13 binary: hi everyone!
07:16 binary: not sure if this is the right place here so sorry if i am false
07:17 binary: since i few days i observe a high memory-usage sometimes after playing a specific game, even after exiting it. the related user-space process seem to be completely gone (can't find anything with top), so i am wondering if that could be a memory leak in the kernel-part?
07:22 binary: is there a way to debug that?
07:26 siddh: Hello, Please take a look at these patches I sent a while ago, and let me know if any further changes are needed. All patches are reviewed once, except the last one which can be ignored. Link: https://lore.kernel.org/lkml/cover.1686075579.git.code@siddh.me/ Thanks.
07:26 siddh: I was thinking of following it up with separating the old macros into a new file (as suggested in earlier discussion). But I can't do that unless the fix is merged.
09:34 senatorM: I am not used to dealing with so big hunks to be expected to be read correctly, but likely bigwuzla does the more advanced way of same thing. Sorts of nodes with values and indexes, coeffs, and bounds.
13:38 KungFuJesus: MrCooper: Yes, I've read that much, like I said I realize I'm probably a decade too late. The mesa-amber project though is meant to make things continue to work with fossilized dinosaur GPUs, or the name would have me believe. I happen to have a dinousaur GPU inside a potato G3
13:40 emersion: is there a reason why the drivers couldn't be ported to DRI2?
13:44 kisak: KungFuJesus: no, mesa-amber isn't a separate project with the goal of keeping fossils working. It's a legacy release branch to keep "classic" (non-gallium) drivers available as a second slotted mesa install. There's no expressed intent to add any hardware to that branch.
13:45 KungFuJesus: emersion: that's what I was sort of getting at, the ML post there had suggested there was a path forward for some of the DRI1 only drivers
13:46 KungFuJesus: The Linux kernel has already killed support after 6.3, so that is yet another thing working against me, there
13:49 emersion: probably because no-one was maintaining it?
13:50 KungFuJesus: yeah I understand the reasons I'm just lamenting the uphill battle of trying to re-enable 3d acceleration on this in 2023
13:52 KungFuJesus: during the transition to DRI2, was there some sort of porting guide / document out there? How similar are these interfaces?
13:53 alyssa: karolherbst: i would but that MR is terrifying
13:54 alyssa: i would say it's old enough that faith is the most qualified reviewer, she has probably forgotten enough of the patches that she can review it herself fairly xP
13:54 KungFuJesus: it looks like having some out of tree module should be possible, the drivers are built as dynamic libraries
13:55 emersion: i don't think that's a good path forward
13:55 KungFuJesus: why's that?
13:56 alyssa: KungFuJesus: to be clear also, the amber/upstream split is more about what's maintained than the age of the part itself
13:57 KungFuJesus: right, this was another obsolence decision that took place at much earlier time than the gallium decision
13:58 < KungFuJes14:16 #nouveau: fdobridge: <k​arolherbst🐧🦀> yeah.. I don't know if userspace can even use it