08:03 phasta: tzimmermann, morning. are you in charge of Bochs?
08:03 phasta: https://lore.kernel.org/all/20241017125145.34729-2-pstanner@redhat.com/
08:04 tzimmermann: phasta, ha! no i sent that patch and i now i wait for a review
08:05 phasta: Ahm? ^^ I'm pretty sure I'm the one who sent it
08:16 tzimmermann: phasta, oh. i just miss interpreted
08:16 tzimmermann: :D
08:16 tzimmermann: i'll have a look
08:16 tzimmermann: sorry, -ECOFFEE
08:25 tzimmermann: looks like it's been fixed already
08:27 phasta: where? on a drm-branch? On 6.12 it's still the old thing
08:45 phasta: ah. Got it
08:56 phasta: In case someone is bored, the GPU scheduler docu patch could maybe make use of a review
08:56 phasta: https://lore.kernel.org/all/20241115103548.90605-2-pstanner@redhat.com/
09:12 tzimmermann: phasta, drm-misc-next at least
09:31 Ermine: more docs are always needed
11:48 Venemo: melissawen: good afternoon, can we talk about this issue? https://gitlab.freedesktop.org/drm/amd/-/issues/3693 I've just tried Cosmic and the issue is very very easy to reproduce
11:53 Venemo: I don't really understand the response from the AMD dev. there is clearly an out of bounds array access which is obviously not fixed in the patch
11:54 Venemo: why would they want to allocate an array of size 3 when there really can be 6 planes?
12:12 colinmarc: @_oftc_nowrep:matrix.org https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31418 broke my app on both h264 and h265, any idea what I might be doing wrong? nothing is jumping out at me
12:13 colinmarc: I'm getting black output in the encode textures, no validation failures or anything else interesting
12:14 colinmarc: I did have a lazy assertion, but I already fixed it (https://github.com/colinmarc/magic-mirror/commit/4f5b34931fc01f1d55e3975ed27355a3e376f067)
12:58 melissawen: Venemo, hey, I talked to AMD folks about this issue at XDC.
12:58 melissawen: AFAIK, surface != planes, so dcn hw supports up to 4 surfaces, even if it can have up to 6 planes
12:59 melissawen: but this mismatch is spread throughtout the driver code
13:00 melissawen: and they need to untangle the issue before changing to 4, as the issue is also part of the DC code and causing regression in other platforms
13:02 melissawen: I see the mismatch in three definitions: MAX_SURFACES, MAX_SURFACE_NUM and MAX_PLANES
13:02 melissawen: it's a mess
13:05 melissawen: the issue was uncovered by the cursor overlay mode.. and they are trying to prevent more than 4 planes first, meanwhile they untangle the whole thing
13:11 melissawen: we have discussed these points here: https://lore.kernel.org/amd-gfx/20241025193727.765195-2-zaeem.mohamed@amd.com/t/#u
13:45 Venemo: I see, thanks
17:28 dcbaker: tarceri_: 44de5f1c46 "glsl: Move ForceGLSLAbsSqrt handling to glsl-to-nir." is getting nominated as a revert, but it doesn't apply cleanly and doesn't look relevant to 24.3, do you want to backport that, or is it cool if I just drop it?
18:01 bl4ckb0ne: is there something in the spec that defines the layout of the images returned by vkGetSwapchainImagesKHR?
18:10 daniels: bl4ckb0ne: define 'layout'
18:11 bl4ckb0ne: VkImageLayout
18:11 bl4ckb0ne: i put it as VK_IMAGE_LAYOUT_UNDEFINED but im not sure
18:17 zamundaaa[m]: bl4ckb0ne: undefined is correct
18:17 bl4ckb0ne: perfect, thanks
20:44 randomsetnow: I must be honest that all my life gangsters as well as governmental fraudsters have been onto my stuff sniffing very close to everything i do, and abuse talking nonsense out, with the worst opportunities given to me, the hardest ever life i managed to change the world , it's 99 percent of my friends are involved in that fraud and get silenced by commands and orders, those details I do
20:44 randomsetnow: not want to talk about. But i already said that I am a bit special, huge moneys are involved to all of them if they keep the "secret" in front of me. But this all i know and it is over for everyone involved.
22:07 sitapeadolete: i learned every trick they ever made, from extortion, to manipulation, very interesting was, what i call as "mass based excess indirect referral/mindbuggling". This type is a neat trick, where the excess talks around only one subject based on that object is targeted, basically by a worlds biggest amount of people alternating in modes that talk about either one subject around the object
22:07 sitapeadolete: which is always me, so to get to the core of real worries later, this is very rare technicue to shut off highest conspiracy and result fixings and things like corruption or abuse case. The issue there is it's known that world needs me as a cow for others, but they want me to not get money for this, and they want everyone feel as special as they want to mindbuggle that it's not me that
22:07 sitapeadolete: they need in the beginning, making infinite seeming set of wrong accusations, but they always everywhere need to talk about me so that it would get my attention not to reveal things when all the sudden ex defense police words in indirect ways came into subject in case everything did go ashtray aka. when i know the truth already that i am the cow. That way they can encode secret messages
22:07 sitapeadolete: wirelessly to me by fake news or something alike. So i would not give away this and this and this amount of people who are so so good etc. and last resort, if this does not work yeaaaahaaaa. it's a war around the corner or just kill off of me before that, which sometimes does not succeed as to how you might have noticed. And why you bother so much is it's you who is sick and you need my
22:07 sitapeadolete: blood and you did wrong things to deserve that.