04:51t61: Hello. I need help installing mesa-amber on Debian 13. Is this the appropriate place to ask? The README from this repo (https://salsa.debian.org/xorg-team/lib/mesa-amber) directed me here.
06:57narmstrong: I have some issues recently with dim trying to push patches to drm-misc-next, I have this weird error `./scripts/get_maintainer.pl: file '&STDIN' doesn't appear to be a patch. Add -f to options?` and then it rejects fully reviewed patches with `Mandatory Maintainer Acked-by missing., aborting` even if the Acked-by is correctly added
06:57narmstrong: Did I miss something ?
07:06robclark: karolherbst: so every fence fd that flows thru enqueue_acquire_gl_objects() gets leaked... where is rusticl closing these?
07:11narmstrong: Hmm ok seems Rob Acked with `Rob Herring (Arm) <robh@kernel.org>` instead of `Rob Herring <robh@kernel.org>`...
16:07kisak: Reinterating, thanks for the XDC talks and everyone involved in that.
18:51emersion: :)
19:03rgallaispou: +1 ! Thanks, there was really inspiring talks and it is really useful to be able to follow the talks online
20:15xeyler: my raspberry pi is panicking after i try to load the panel-mipi-dbi driver on boot. here's the stack trace: https://0x0.st/KMHI.txt
20:16xeyler: the kernel is technically tainted because it's the raspberry pi foundation's fork of the kernel. as far as i'm aware, it's very similar to upstream, but i'm willing to try booting mainline if it's a problem
20:18xeyler: in any case, what seems to be going on is the kernel is having trouble initializing two framebuffer devices. i think the kernel is assigning the pi's gpu fb0 and it's trying to assign panel-mipi-dbi fb0 as well (struct member fb_info.node selects the '0' in fb0, i believe)
20:21xeyler: can anyone help me know if this is some bug that needs to be addressed upstream or if i just need to change something about my configuration?
20:23xeyler: i guess i would have expected the drm subsystem to have some sort of mutex on framebuffer device creation and increment fb_info.node if a framebuffer with the corresponding node id already exists