ChanServ changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - Logs https://oftc.irclog.whitequark.org/panfrost - <macc24> i have been here before it was popular
atler is now known as Guest1506
atler has joined #panfrost
Guest1506 has quit [Ping timeout: 480 seconds]
camus1 has joined #panfrost
camus has quit [Ping timeout: 480 seconds]
camus has joined #panfrost
camus1 has quit [Ping timeout: 480 seconds]
davidlt has joined #panfrost
camus1 has joined #panfrost
camus has quit [Read error: Connection reset by peer]
davidlt has quit [Ping timeout: 480 seconds]
vstehle has quit [Ping timeout: 480 seconds]
vstehle has joined #panfrost
wwilly__ has joined #panfrost
nlhowell has joined #panfrost
wwilly_ has quit [Ping timeout: 480 seconds]
wwilly__ has quit []
wwilly has joined #panfrost
davidlt has joined #panfrost
anarsoul has quit [Ping timeout: 480 seconds]
anarsoul has joined #panfrost
warpme_ has joined #panfrost
rasterman has joined #panfrost
camus has joined #panfrost
camus1 has quit [Ping timeout: 480 seconds]
dante6913 has joined #panfrost
dante6913 has quit []
camus1 has joined #panfrost
camus has quit [Ping timeout: 480 seconds]
<bbrezillon> stepri01: I've been reviewing tomeu's vkEvent MR, and it appeared to me that supporting 'synchronization' jobs (jobs with job->head = 0 whose only purpose is to add a synchronization point) would be a good replacement for the 'NULL' job emitted here
<bbrezillon> stepri01: IOW, would you be okay with this change => https://gitlab.freedesktop.org/bbrezillon/linux/-/commit/30132ab93890d1693c1fc6fdc391e412cda11720 ?
<bbrezillon> we'd keep the 'if (submit->jc != 0) return -EINVAL' in the old submit ioctl of course
<stepri01> bbrezillon: I'm not sure whether special casing head==0 is best, or introducing a new JD_REQ
<stepri01> kbase has the concept of "dependency only atoms" which is implemented with a special 'requirement'
urja has quit [Remote host closed the connection]
<bbrezillon> sure, a JD_REQ flag would work too
urja has joined #panfrost
<stepri01> that would be my preference
<bbrezillon> perfect, I'll go for this solution then
alpernebbi has joined #panfrost
<stepri01> 👍
wwilly has quit [Ping timeout: 480 seconds]
wwilly has joined #panfrost
<alyssa> robmur01: ping
rasterman has quit [Quit: Gettin' stinky!]
rasterman has joined #panfrost
wwilly has quit [Ping timeout: 481 seconds]
<alyssa> alyssa: util_blitter_save_so_targets call is probably wrong
<alyssa> so is save_vertex_shader
camus has joined #panfrost
camus1 has quit [Remote host closed the connection]
<alyssa> do we need to preserve min_samples?
<robmur01> alyssa: 'sup
<alyssa> robmur01: who do i need to hassle to get sven's DART patches pushed 😇
<robmur01> I'll try to give them a second look over soon, although where we are in the cycle it's probably at least a couple of weeks still until new stuff starts getting queued again
* alyssa isn't familiar with said cycle for other subsystems
<robmur01> I can't remember off-hand if Joerg has a particular preference, but it's not uncommon for maintainers to focus just on fixes early on and not start their for-next queue until around rc3
<robmur01> certainly don't use drm-misc as a benchmark for the rest of the kernel ;)
camus1 has joined #panfrost
camus has quit [Ping timeout: 480 seconds]
atler has quit [Quit: atler]
atler has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
davidlt has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Quit: alpernebbi]
Rathann has joined #panfrost
anholt has quit [Remote host closed the connection]
rasterman has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
Rathann has quit [Remote host closed the connection]
warpme_ has quit [Quit: Connection closed for inactivity]
Daanct12 has joined #panfrost
Daanct12 has quit [Remote host closed the connection]