02:31 HdkR: karolherbst: btw, how soon until you implement freesync/HDMI-VRR in Nouveau? :D
02:38 imirkin: well, the patches for HDMI 2.0 just made it to drm-next
02:38 imirkin: so use your judgement
03:03 imirkin: and not even all of hdmi2... just the high-frequency stuff
03:03 imirkin: i'm still planning on doing high-bpc and yuv420
03:03 HdkR: woo
07:22 mupuf: karolherbst: isn't the answer obvious? We just suck at PM? :D
11:17 karolherbst: mupuf: no... I mean, I am sure I do everything right from the point where we read out the values
11:17 karolherbst: but... the values are too high reported by the sensor?
11:20 mupuf: karolherbst: why not apply the same logic for reading the values when running on the blob and ocmparing values?
11:20 karolherbst: I did
11:20 mupuf: and what results did you get?
11:20 karolherbst: under nouveau the shunt values are higher
11:30 karolherbst: mupuf: I was able read out the i2c sensor under nvidia and get to the same value nvidia-smi was reporting. Doing the same with nouveau gets me to nouveaus reported values ;) But... those just seem way too high
11:30 karolherbst: nouveaus ones
11:30 mupuf: so, it means the current is highrr
11:30 mupuf: hence why I was saying the PM is shit
11:31 mupuf: what magic are you expecting here?
11:32 karolherbst: mupuf: but it didn't fit with the temparature of the GPU :/
11:32 mupuf: unless you can force the EC to rotate the fans at a constant speed, don't pay too much attention to that
11:33 karolherbst: I can read out the fan speeds
11:33 karolherbst: and also force a speed if I actually wanted to
11:56 mupuf: karolherbst: try it then
11:56 mupuf: and compare with the EC-reported power consumption
12:00 karolherbst: mhh, random thought: turning the GPU on/off should actually work on that machine, maybe I could diff the EC reported consumption with the I2C one ones the GPU comes back on... allthough I have no idea how much power consumption we might have left if the GPU is actually suspended
12:11 karolherbst: mupuf: mhh, +15W on the GPU sensors, but only +10W on the EC values
12:13 mupuf: I wonder if there is a broken reference voltage on nouveau
12:13 mupuf: but I would assume they would use a zener diode as a reference voltage
12:14 karolherbst: mhh, maybe we have to calibrate something?
12:24 gst568923: hi guys I have two graphics card Intel and Nvidia and I would like to know what is the difference between VAAPI i965 and mesa-va-drivers
12:27 karolherbst: gst568923: I doubt intel supports the latter
12:27 karolherbst: dunno though, ask in #intel-gfx
12:29 karolherbst: mupuf: funny thing though, the GPU tries real hard to cap at 30W on battery, but totally fails to do that as we get over that by just idling...
12:29 gst568923: karolherbst I have read this https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-VAAPI-Samsung-Patches , means that Intel Vaapi can be used with nouveau driver?
12:29 karolherbst: gst568923: why would you want to use nouveau for video acceleration?
12:29 karolherbst: turning the GPU on just to watch a video where the Intel chip is already good enough?
12:30 gst568923: karolherbst I have: the video monitor connector are: VGA into motherboard and VGA/DVI into Nvidia GF119, I have connected the monitor into DVI
12:30 karolherbst: doesn't matter
12:31 karolherbst: or is this a desktop and you only want to use nouveau?
12:31 karolherbst: or well, the nvidia GPU is on all the time anyway
12:32 gst568923: karolherbst yes is a desktop I would like use the video acceleration but I have a problem with blob firmware NVD9
12:32 gst568923: karolherbst then I would like to know if I can use vaapi or vaapi-copy
12:33 karolherbst: you can use vdpau afaik
12:33 gst568923: vdpau require a blob firmware
12:35 karolherbst: that doesn't change with vaapi
12:40 gst568923: karolherbst but libvdpau-va-gl1 (VDPAU driver with OpenGL/VAAPI backend) what is it for?
12:40 karolherbst: this allows vdpau only application to be used with vaapi only drivers
12:46 gst568923: then for use vaapi video decoder I have to install the drivers: i965-va-driver or mesa-va-drivers?
12:55 karolherbst: the former
16:14 moaz: hello
16:15 moaz: "vdpau" is showing "not supported" for all decoders on my machine
16:15 moaz: er, "vdpauinfo"
16:15 moaz: is this likely a software issue or does nouveau truly not support any decoder for this GPU?
16:15 moaz: it's a mobile GPU, GT280M
16:16 endrift: moaz: I'm under the impression (I may be wrong) that nouveau doesn't support vdpau but does support vaapi
16:17 moaz: vainfo: Supported profile and entrypoints
16:17 moaz: VAProfileNone : VAEntrypointVideoProc
16:17 moaz: no codecs listed there either
16:17 endrift: ah I just looked at the feature matrix
16:17 endrift: it's supported but you need firmware
16:17 moaz: ah, I see
16:18 moaz: well, I try to stay as libre as possible, so firmware is out of the question
16:18 moaz: guess I'll have to stick to CPU rendering then?
16:18 endrift: I'd wait around for someone more knowledgeable on this than me
16:19 moaz: okay
16:21 endrift: I also found this page on the wiki: https://nouveau.freedesktop.org/wiki/VideoAcceleration/
17:10 karolherbst: endrift: nouveau supports vdpau
17:19 endrift: karolherbst: yeah I saw that after I looked it up
19:05 orbea: supports as in sometimes it works fine, other times it ends up in a broken pixelated mess
22:39 RSpliet: moaz: endrift is perfectly knowledgable... video decoding requires firmware that we can't redistribute
22:39 moaz: just to be clear, I'm not the one who implied that he isn't knowledgeable
22:39 RSpliet: I know :-)
22:40 moaz: but thanks for the (unfortunate) info :-)
22:40 moaz: have a nice day