ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
ybogdano has joined #dri-devel
mhenning has joined #dri-devel
ybogdano has quit [Read error: Connection reset by peer]
kts has joined #dri-devel
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
bbrezillon has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
Akari has quit [Read error: Connection reset by peer]
Akari has joined #dri-devel
<HdkR> linkmauve: mesa should already have xxhash inside of it, time to update to xxh3 and move the hash over? :P
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
RAOF_ has joined #dri-devel
Akari has quit [Ping timeout: 480 seconds]
aravind has joined #dri-devel
dakr has quit [Ping timeout: 480 seconds]
Akari has joined #dri-devel
smaeul has quit [Quit: Down for maintenance...]
chipxxx has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
smaeul has joined #dri-devel
bmodem has joined #dri-devel
smaeul has quit [Read error: Connection reset by peer]
bmodem has quit []
bmodem has joined #dri-devel
kem has quit [Ping timeout: 480 seconds]
smaeul has joined #dri-devel
bmodem1 has joined #dri-devel
bmodem has quit [Read error: Connection reset by peer]
kem has joined #dri-devel
pallavim has joined #dri-devel
heat_ has quit [Ping timeout: 480 seconds]
thellstrom has joined #dri-devel
Moe_Icenowy has joined #dri-devel
MoeIcenowy has quit [Read error: Connection reset by peer]
RAOF_ has left #dri-devel [#dri-devel]
aravind has joined #dri-devel
slattann has joined #dri-devel
soreau has quit [Read error: Connection reset by peer]
soreau has joined #dri-devel
jewins has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
mhenning has quit [Quit: mhenning]
Duke`` has joined #dri-devel
kts has joined #dri-devel
sdutt has quit [Read error: Connection reset by peer]
RAOF_ has joined #dri-devel
itoral has joined #dri-devel
tzimmermann has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
RAOF_ has quit [Ping timeout: 480 seconds]
thellstrom has quit [Ping timeout: 480 seconds]
Haaninjo has joined #dri-devel
fab has joined #dri-devel
danvet has joined #dri-devel
RAOF_ has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
pallavim has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest1064
srslypascal has joined #dri-devel
pallavim has joined #dri-devel
Guest1064 has quit [Ping timeout: 480 seconds]
aravind has joined #dri-devel
lemonzest has joined #dri-devel
hch12907 has quit [Quit: Reconnecting]
hch12907 has joined #dri-devel
epoll has quit [Ping timeout: 480 seconds]
hch12907__ has joined #dri-devel
epoll has joined #dri-devel
lygstate has quit [Read error: Connection reset by peer]
hch12907__ has quit []
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
chipxxx has quit [Remote host closed the connection]
chipxxx has joined #dri-devel
gouchi has joined #dri-devel
gouchi has quit [Remote host closed the connection]
Jeremy_Rand_Talos__ has quit [Remote host closed the connection]
Jeremy_Rand_Talos__ has joined #dri-devel
Haaninjo has quit [Ping timeout: 480 seconds]
fab has quit [Quit: fab]
chipxxx has quit [Ping timeout: 480 seconds]
fab has joined #dri-devel
bbrezillon has joined #dri-devel
tursulin has joined #dri-devel
<ccr> zmike, it was! \:D\
* ccr cheers at zmike
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
jkrzyszt has joined #dri-devel
kts has quit []
kts has joined #dri-devel
sarahwalker has joined #dri-devel
rasterman has joined #dri-devel
lynxeye has joined #dri-devel
<linkmauve> HdkR, it does, my question is whether any maintainer thinks something in their driver would break from that change.
<linkmauve> But I could just give it a try and see for myself, CI will certainly tell. ^^
lemonzest has quit [Quit: WeeChat 3.5]
rasterman has quit [Quit: Gettin' stinky!]
fahien has joined #dri-devel
vliaskov has joined #dri-devel
RAOF_ has quit [Ping timeout: 480 seconds]
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
mvlad has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
pcercuei has joined #dri-devel
Haaninjo has joined #dri-devel
Haaninjo has quit [Remote host closed the connection]
lemonzest has joined #dri-devel
rasterman has joined #dri-devel
<tomeu> danvet: btw, did you have time to see the latest DRM CI series?
fahien has quit [Ping timeout: 480 seconds]
fahien has joined #dri-devel
warpme___ has quit []
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
kts has quit []
devilhorns has joined #dri-devel
pochu has quit [Quit: Lost terminal]
bmodem1 has quit []
kts has joined #dri-devel
rgallaispou has quit [Ping timeout: 480 seconds]
fahien has quit [Ping timeout: 480 seconds]
<tjaalton> how to get mesa !15058 merged?
<emersion> is it reviewed?
<emersion> tjaalton: can you add S-o-b and R-b tags to the commit message?
<tjaalton> emersion: it's not my mr
<tjaalton> but I poked the guy who owns it
anholt_ has joined #dri-devel
bmodem has joined #dri-devel
rgallaispou has joined #dri-devel
anholt has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
pallavim has quit [Remote host closed the connection]
pallavim has joined #dri-devel
kts has joined #dri-devel
fahien has joined #dri-devel
MajorBiscuit has joined #dri-devel
fahien has quit [Ping timeout: 480 seconds]
Surkow|laptop has quit [Quit: 418 I'm a teapot - NOP NOP NOP]
Surkow|laptop has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
pochu has joined #dri-devel
iokill_ has left #dri-devel [#dri-devel]
iokill has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
kts has quit []
fab has quit [Quit: fab]
fab has joined #dri-devel
zep has joined #dri-devel
mbrost has joined #dri-devel
zep has quit []
DemiMarie is now known as Guest1080
itoral has quit []
underpantsgnome[m] has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
<eric_engestrom> the qsort_r part of that MR has a better fix here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18527
mbrost has quit [Ping timeout: 480 seconds]
tursulin has quit [Quit: Konversation terminated!]
sdutt has joined #dri-devel
tursulin has joined #dri-devel
jewins has joined #dri-devel
fahien has joined #dri-devel
mszyprow has joined #dri-devel
dakr has joined #dri-devel
wens has joined #dri-devel
rgallaispou1 has joined #dri-devel
rgallaispou has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
rgallaispou has joined #dri-devel
rgallaispou1 has quit [Read error: Connection reset by peer]
bmodem has joined #dri-devel
zehortigoza has quit [Remote host closed the connection]
fab has quit [Quit: fab]
fab has joined #dri-devel
fab has quit []
zehortigoza has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
MajorBiscuit has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
lemonzest has quit [Quit: WeeChat 3.5]
fahien1 has joined #dri-devel
fahien has quit [Ping timeout: 480 seconds]
fahien1 is now known as fahien
sdutt has quit []
sdutt has joined #dri-devel
MajorBiscuit has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
<kisak> meh, !18719 closes non-public issue #7285, therefore I don't know if that helps anything in the wild and decide if I should fast track it.
<kisak> must not be super critical and can wait for 22.2.1.
mszyprow has quit [Ping timeout: 480 seconds]
fahien1 has joined #dri-devel
fahien is now known as Guest1086
fahien1 is now known as fahien
ybogdano has joined #dri-devel
Guest1086 has quit [Ping timeout: 480 seconds]
Duke`` has joined #dri-devel
wens has left #dri-devel [#dri-devel]
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
jfalempe has quit [Quit: Leaving]
slattann has quit [Quit: Leaving.]
<ajax> this job is now consistently timing out, but not in the same place every time, and i have no idea how i'd have caused it
mszyprow has joined #dri-devel
jfalempe has joined #dri-devel
fab has joined #dri-devel
tzimmermann has quit [Quit: Leaving]
rasterman has joined #dri-devel
fxkamd has quit []
aravind has joined #dri-devel
<jenatali> zmike: ugh. Disable the test I guess? I won't be able to take a closer look for a few weeks. If you do disable it, file an issue for me to re-enable it?
<zmike> uhhhhhhh
fahien has quit [Ping timeout: 480 seconds]
tursulin has quit [Ping timeout: 480 seconds]
fahien has joined #dri-devel
ella-0_ has joined #dri-devel
MajorBiscuit has quit [Ping timeout: 480 seconds]
heat_ has joined #dri-devel
ella-0- has joined #dri-devel
pcercuei has quit [Read error: Connection reset by peer]
pcercuei has joined #dri-devel
ella-0 has quit [Read error: Connection reset by peer]
sarahwalker has quit [Remote host closed the connection]
ella-0_ has quit [Read error: Connection reset by peer]
devilhorns has quit []
mszyprow has quit [Ping timeout: 480 seconds]
aravind has quit [Ping timeout: 480 seconds]
fahien1 has joined #dri-devel
fahien has quit [Ping timeout: 480 seconds]
kem has quit [Ping timeout: 480 seconds]
<zmike> dcbaker: \o/
* dcbaker is just glad to have it done
gouchi has joined #dri-devel
gouchi has quit []
kem has joined #dri-devel
fahien1 is now known as fahien
<MrCooper> ajax: tried bisecting the commit from that MR which triggers the timeout?
lemonzest has joined #dri-devel
mbrost has joined #dri-devel
kem has quit [Ping timeout: 480 seconds]
lynxeye has quit [Quit: Leaving.]
ybogdano has quit [Remote host closed the connection]
mattst88 has quit [Read error: Connection reset by peer]
mattst88 has joined #dri-devel
kem has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
heat has joined #dri-devel
heat_ has quit [Read error: No route to host]
MajorBiscuit has joined #dri-devel
ngcortes has joined #dri-devel
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit []
MajorBiscuit has quit [Ping timeout: 480 seconds]
pendingchaos has quit [Ping timeout: 480 seconds]
jkrzyszt has quit [Ping timeout: 480 seconds]
fahien has quit [Quit: fahien]
pendingchaos has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
mbrost_ has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
kts has joined #dri-devel
Haaninjo has joined #dri-devel
kts has quit []
kts has joined #dri-devel
mbrost_ has quit [Ping timeout: 480 seconds]
iive has joined #dri-devel
lemonzest has quit [Quit: WeeChat 3.5]
<mdnavare> vsyrjala: jadahl: One of the concerns in Mutter community expressed about enabling VRR in this MR https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1154 was that since VRR enabling needs a full modeset to program VRR regs, this will blank the screen everytime VRR is enabled. What are your thoughts on addressing this?
<mdnavare> vsyrjala: One of the solutions we discussed earlier was change the kernel code to always compute and configure VRR parameters when supported by panel , just dont enable it in atomic commit until requested by userspace. So then in that case we dont need a full modeset when requested by userspace. Is this a good approach forward, jadahl, would this address your concern expressed in this Mutter MR?
<mdnavare> MrCooper: Do you know if AMD enables the VRR in the same way where always the VRR params are computed and committed only when requested by userspace?
ngcortes has quit [Ping timeout: 480 seconds]
danvet has quit [Ping timeout: 480 seconds]
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
heat has quit [Read error: No route to host]
heat has joined #dri-devel
<agd5f> mdnavare, we even use vrr to do seemless mode switches between different refresh rates. E.g., for media apps that want to change from 60 to 24 fps during playback
<mdnavare> agd5f: And that is requested through any property from userspace ?
<mdnavare> agd5f: That would be I guess the fixed average refresh rate mode right?
<agd5f> you just do a modeset and it will use vrr to change the refresh rather than doing a full modeset so the screen doesn't blank
<mdnavare> I am guessing for that use case the VRR_enabled CRTC property stays false right? That sets to tru only for a true variable refresh for full screen games
<agd5f> right.
<mdnavare> agd5f: And thats only for DP 2.0 and HDMI 2.1 onwards correct?
<mdnavare> agd5f: But wont it still need a full modeset to recompute new parameters for different refresh rate?
<agd5f> mdnavare, any DP that supports variable refresh rate
<agd5f> IIRC pre DP 2.0 supported it as well
rgallaispou1 has joined #dri-devel
<agd5f> I guess we calculate for the max refresh and then at modeset time, if we see that the rate is within the range of the monitor, we just change the rate
<agd5f> hwentlan_, ^^^ do you remember the details?
rgallaispou has quit [Ping timeout: 480 seconds]
<mdnavare> agd5f: Yes that sounds correct, but then at modeset to change to that different rate, would need to reprogram VRR params which would need a full modeset I believe
mvlad has quit [Remote host closed the connection]
<agd5f> I think you just set the min and max and you are done, at least on our hw
<tleydxdy> on my monitor at least the vrr range only go down to 90hz, so it would still blank out?
<tleydxdy> say if the desktop is 60hz
<agd5f> if the refresh rate is outside of the vrr range, then it would need a full modeset, but is that actually a thing?
<tleydxdy> or in this case the desktop will always run at the max refresh rate, and it's allowing fullscreen apps to go below that?
kts has quit [Ping timeout: 480 seconds]
<mdnavare> agd5f: Thanks for the inputs, on our HW we need to program a few more params that are derived from min and max , but I think we can change the code a bit to always program these so we wont need a full modeset and then when requested we just commit it
<mdnavare> vsyrjala: Do you agree?
fab has quit [Quit: fab]
MajorBiscuit has joined #dri-devel
<vsyrjala> yeah, i think we should be able to at least some stuff with the vrr hardware
<vsyrjala> i think tgl+ can also repgram the normal vtotal register on the fly. i guess you can think of that as basically a totally manual vrr mode or something
<vsyrjala> i just wish someone figured out what's causing that vrr black screen bug
<vsyrjala> not really motivated to add stuff on top of a buggy foundation
<mdnavare> vsyrjala: So I will start writing up patches then toc hange our vrr_compute_config to always compute vrr parameters and then writing to regs in commit tail only when vrr crtc property set
Duke`` has quit [Ping timeout: 480 seconds]
<mdnavare> vsyrjala: The other thing I wanted to clarify is how should we handle a scenario where userpsace requests VRR on a non VRR panel, currently we dont reject or throw a warning we just continue without vrr, but that is not something that userspace expects, so how do we communicate that to userspace
<tleydxdy> maybe just have a way to check if vrr is actually enabled?
<tleydxdy> so apps that didn't care continue to work
<mdnavare> so for that we will need to expose the actual vrr crtc state back to userspace through a prop or debugfs
ybogdano has joined #dri-devel
pallavim has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Ping timeout: 480 seconds]
vliaskov has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
apinheiro has joined #dri-devel
iive has quit [Quit: They came for me...]
pcercuei has quit [Quit: dodo]
apinheiro has quit [Quit: Leaving]
Haaninjo has quit [Quit: Ex-Chat]