clamor has quit [Read error: Connection reset by peer]
clamor has joined #dri-devel
fab has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
valentine has quit [Quit: Reconnecting]
valentine has joined #dri-devel
<daniels>
mlankhorst: I'm applying a fix commit to drm-misc for a commit which is in drm-misc-next (as well as the PR airlied sent to Linus for 6.17) and has been applied there, but is not in drm-misc-fixes as that hasn't had a backmerge yet. am I right to think that I should be pushing it to drm-misc-next-fixes, so the next fixes-for-6.17 pull req includes it?
<mlankhorst>
daniels: That's the correct place!
<mlankhorst>
Or if it can wait until monday I'd put it in rc1
<daniels>
\o/
<daniels>
it's not super-urgent, so happy to do whatever's easiest for you, as long as it gets into 6.17 at some stage
YuGiOhJCJ has quit []
<mlankhorst>
just put it in next-fixes, I don't think it has been pulled in yet so it doesn't matter in either case
<mareko>
zmike: an explanation how the multi-context buffer release works
<mareko>
there should be a large comment somewhere for any non-trivial stuff
lumidify has quit [Quit: leaving]
lumidify has joined #dri-devel
lsntvt__ has joined #dri-devel
sarnex has quit []
nerdopolis has quit [Read error: Connection reset by peer]
nerdopolis has joined #dri-devel
sarnex has joined #dri-devel
clamor has quit [Ping timeout: 480 seconds]
clamor has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
clamor has quit [Ping timeout: 480 seconds]
clamor has joined #dri-devel
cmichael has joined #dri-devel
rtauro has joined #dri-devel
sima has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
<zmike>
mareko: I did explain it some, and I can add more comments, but in general are we good to go? if so I'll start reorganizing things into commits that might actually be merge-able
kts has joined #dri-devel
rtauro has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
clamor has quit [Read error: Connection reset by peer]
<mareko>
zmike: in general yes, but I still need to review the multi-context stuff
SquareWinter68_ has joined #dri-devel
SquareWinter68 has quit [Ping timeout: 480 seconds]
cmichael has quit [Quit: Leaving]
fab has joined #dri-devel
<mareko>
what is the different between load_global, load_global_constant, and load_constant?
Sid127 has joined #dri-devel
<mareko>
nevermind load_constant, but what about load_global_constant?
caitcatd- has joined #dri-devel
valpackett_ has joined #dri-devel
valpackett_ has quit [Ping timeout: 480 seconds]
<glehmann>
I think there isn't really a difference, at least if the load_global is flaged as ACCESS_CAN_REORDER
<glehmann>
so load_global_constant should probably be removed at some point
dviola has joined #dri-devel
<karolherbst>
mareko: load_global_constant is considered to load from a constant buffer that never changes
<karolherbst>
or at least not while the shader is executing
<austriancoder>
I want to "transport" the action (begin, pause, resume, end) of transform feedback down into the gallium driver. At the moment I have some wild logic in the gallium driver to guess the action based on pipe->set_stream_output_targets(..) calls. My HW has one register which wants the current xfb state: enabled, paused/stopped or resumed.
<austriancoder>
shall I extend set_stream_output_targets(..) with a hint argument?
fab has quit [Ping timeout: 480 seconds]
<austriancoder>
or maybe add a new set_stream_output_state(..)
edolnx has quit [Ping timeout: 480 seconds]
edolnx has joined #dri-devel
edolnx_ has joined #dri-devel
edolnx has quit [Ping timeout: 480 seconds]
haaninjo has quit [Quit: Ex-Chat]
epoch101 has joined #dri-devel
edolnx has joined #dri-devel
Jeremy_Rand_Talos has quit [Remote host closed the connection]