stikonas has quit [Remote host closed the connection]
shadeslayer9 has joined #panfrost
tomeu6 has joined #panfrost
tomeu has quit [Read error: Connection reset by peer]
tomeu6 is now known as tomeu
shadeslayer has quit [Ping timeout: 265 seconds]
shadeslayer9 is now known as shadeslayer
alyssa has quit [Ping timeout: 272 seconds]
vstehle has quit [Ping timeout: 256 seconds]
davidlt has joined #panfrost
robmur01_ has joined #panfrost
robmur01 has quit [Ping timeout: 256 seconds]
bbrezillon has quit [Ping timeout: 260 seconds]
bbrezillon has joined #panfrost
buzzmarshall has quit [Remote host closed the connection]
_whitelogger has joined #panfrost
vstehle has joined #panfrost
raster has joined #panfrost
warpme_ has joined #panfrost
stikonas has joined #panfrost
robmur01_ is now known as robmur01
<macc24>
sooo xonotic on midgard runs and is playable at 1280x800 with lowest settings on panfrost
<macc24>
on opengl 2.1
<HdkR>
coolio
<macc24>
yea
<macc24>
bottleneck is on cpu
<HdkR>
It would probably get worse with GL3.x as well if it is doing indexed draws. Since there is the minmax calculation
<macc24>
can i test gl3 on panfrost without compiling mesa?
<HdkR>
PAN_MESA_DEBUG=gl3
<HdkR>
Looking forward to Valhall removing that overhead
<macc24>
xonotic reports gl2.1 still
<macc24>
mesa is at 20.1.5
<HdkR>
Too old
<macc24>
setting MESA_NO_ERROR to one helped with performance a bit
<HdkR>
It's in 20.2.0-rc1 at least
<raster>
oh wow... what changed... i no longer see scheduling evilness when you have a client rendering as fast as it can and wl compositor also fighting fore the cpu...
<raster>
(midgard panfrost)
<raster>
niiiiiiiiiiiiice
<raster>
updated to 5.8 rc6 and latest git master mesa...
<raster>
kernel change of some sort i assume... didnt see it
<macc24>
huh?
<daniels>
turning on afbc is even more turbo mode :)
<raster>
ok - a few weeks back in my last update - i run a benchmark that has fairly simple rendering that is like rendering 200+ large alpha quads in 1080p as fast as it can
<raster>
like that ... and basically it would, client-side, appear to get like 40fps... but visible only like 1-2fps as the compositor (wl compositor) couldn't get in enough gpu cycles to push out frames - so a gpu scheduling problem.
<HdkR>
Nice, perfect bench to utilize tiled rendering
<raster>
but now i get a good solid output that is "smooth" that represents the input
<raster>
so something got fixed in scheduling between 5.7 and 5.8 :)
<raster>
i've been busy with other things and not updating lately...
<raster>
there was a mysterious bug with pae address translation i was trying to figure out that only happened in this benchmark - possibly because some command queue or something kept growing and growing... that was a guess. now the bug no longer happens too.
<robmur01>
hmm, I would not expect to see anything from the pagetable code unless something was seriously broken, i.e. more than just poor scheduling
<robmur01>
the pagetables should pretty much just be following the state of the DRM MM
raster has quit [Remote host closed the connection]
stikonas has quit [Remote host closed the connection]
<alyssa>
'
<alyssa>
]|\']\[-
<alyssa>
sorry
<alyssa>
tomeu: bbrezillon: as discussed mainline panfrost has issue on rk3399 chromebooks due to... power? maybe?
<alyssa>
I guess a patch never landed to fix that (?) -- do we know what's up there?
<alyssa>
blocking AFBC stuff, since a single byte off means one wrong pixel with linear but the entire block corrupting with afbc
<alyssa>
also robmur01 robher ^
<robmur01>
patches to make regulators work properly again have just landed in drm-misc-next, I think
<alyssa>
ack
<alyssa>
oh, really 'just', ok
<urjaman>
so.... 5.9 will work? :P
<alyssa>
guess who gets to recompile the kernel again ;p
<robmur01>
...or dial back to 5.4 LTS :P
<alyssa>
:P
<urjaman>
i haven't moved anywhere from 5.4
<alyssa>
robmur01: I'm trying to get AFBC-down-the-whole-stack since it ~~makes for better marketing~~ saves power.
<alyssa>
and RK3399 display AFBC landed in like 5.8
<robmur01>
TBH I'd imagine saving memory traffic and thus latency is probably even more significant than power for most of our "cheap TV box SoC" boards
<alyssa>
yeah
<robmur01>
an immediate alternative would be trying to revert 221bc77914cb, but it'll be messy
<alyssa>
in the pathological case, something like glmark2-es2 -btexture jumps up hundreds of FPS from u-interleaved to AFBC
<robmur01>
I shall have to try AFBC with rvgl - started playing with that recently and framerates are all over the shop for no obvious reason
<robmur01>
(also some minor glitches, but I guess I'd have to futz with an apitrace to be allowed to complain...)
kaspter has quit [Quit: kaspter]
unoccupied has joined #panfrost
davidlt has quit [Ping timeout: 256 seconds]
stikonas has joined #panfrost
buzzmarshall has joined #panfrost
awordnot has quit [Read error: Connection reset by peer]
tomboy65 has quit [Remote host closed the connection]
awordnot has joined #panfrost
tomboy65 has joined #panfrost
stikonas has quit [Remote host closed the connection]
stikonas has joined #panfrost
tomboy65 has quit [Remote host closed the connection]
tomboy65 has joined #panfrost
stikonas has quit [Remote host closed the connection]
buzzmarshall has quit [Remote host closed the connection]
rokquarry has joined #panfrost
rokquarry has quit [Client Quit]
warpme_ has quit [Quit: Connection closed for inactivity]