02:49airlied: mupuf: so problem with navi21? https://gitlab.freedesktop.org/mesa/mesa/-/jobs/54615025
06:29airlied: zzoon[m]: okay the anv av1 decoder is decoding one frame, subsequenct frames aren't correct
07:30mupuf: airlied: FFS, yes
07:30mupuf: thanks!
11:23mripard: narmstrong: -fixes should be fixed now
11:25narmstrong: mripard: indeed, perfect thx
18:24zmike: mareko: is the reason radeonsi doesn't export PIPE_CAP_ALLOW_DYNAMIC_VAO_FASTPATH because it has vstate draws?
19:24carbonfiber: I got a historical question. As far as I can see, then xf86-input-evdev was released in 2004. But evdev is from 1999. Was there a different X11 evdev driver before xf86-input-dev existed?
19:25carbonfiber: before xf86-input-evdev existed*
19:43urja: 2004 is also the year Xorg was forked from XFree86, so ... check if XFree86 had an evdev driver?
19:52carbonfiber: urja: I tried that already. Could not find anything. But not sure if that is because I am bad at finding it, or because it did not exist.
19:53airlied: I think nobody cared before 2004 about using evdev and just used keyboard/mouse drivers
19:54carbonfiber: but then I have a follow up question. What was evdev used for if not for X11 input?
19:56airlied: the console used them initially
19:56urja: gamepads?
19:56urja: i'm not sure lol
20:01carbonfiber: ok. not trying to be annoying with all these follow-up questions. but why did the console use evdev instead of just using the keyboard? I don't really associate the linux console with needing anything more than a "dumb" keyboard?
20:12airlied: usb keyboards I think changed things
20:32carbonfiber: ok. thanks.
20:35airlied: I think there were also some hacky mouse/keyboard patches to use evdev for a while that never got upstream
21:09zzoon[m]: <airlied> "zzoon: okay the anv av1 decoder..." <- great news! I'm going to take a look after travelling.