alyssa changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - Logs https://freenode.irclog.whitequark.org/panfrost - <daniels> avoiding X is a huge feature
Depau has joined #panfrost
Depau_ has quit [Ping timeout: 256 seconds]
vstehle has quit [Ping timeout: 260 seconds]
indy_ has quit [Ping timeout: 240 seconds]
kaspter has joined #panfrost
unoccupied has quit [Quit: WeeChat 2.8]
buzzmarshall has quit [Remote host closed the connection]
_whitelogger has joined #panfrost
davidlt has joined #panfrost
vstehle has joined #panfrost
unoccupied has joined #panfrost
_whitelogger has joined #panfrost
nlhowell has joined #panfrost
<endrift> alyssa: I've started getting to the point where if I want to cherry-pick things between branches that I just committed I'll just `git checkout whatever && git cherry-pick HEAD@{1}` because I have become too powerful
<endrift> this is what reflog let me become
tomboy65 has quit [Remote host closed the connection]
tomboy64 has joined #panfrost
indy has joined #panfrost
nlhowell has quit [Ping timeout: 246 seconds]
yann has joined #panfrost
guillaume_g has joined #panfrost
stikonas has joined #panfrost
<HdkR> Got myself an x86-64 panfrost build, now I just need to setup a board to run it
Werner has quit [Changing host]
Werner has joined #panfrost
icecream95 has joined #panfrost
raster has joined #panfrost
awordnot has quit [Ping timeout: 264 seconds]
yann has quit [Ping timeout: 240 seconds]
yann has joined #panfrost
<tomeu> HdkR: what could go wrong? :p
nlhowell has joined #panfrost
kaspter has quit [Ping timeout: 260 seconds]
camus1 has joined #panfrost
camus1 is now known as kaspter
<icecream95> alyssa: AlphaEnabled is different from alpha.enabled, so it should have been obvious that there was code in the middle that could be changed...
<icecream95> Keeping the assert will remind me to add lowering in Nine, for which support should be coming Soon™
<icecream95> It's not easy debugging x86 code in a buggy emulator when you haven't even got a compiler set up
icecream95 has quit [Ping timeout: 260 seconds]
rak-zero has quit [Read error: Connection reset by peer]
nlhowell has quit [Ping timeout: 240 seconds]
TheMojoMan has joined #panfrost
awordnot has joined #panfrost
TheMojoMan has quit [Quit: Connection closed]
<warpme_> guys: I just gave try for current mesa master on mali450/t720/t820/t860/g31 and all works ok except t720. errant t720 (allwinner h6) gives screen like this: https://paste.pics/aa5877a2bea3b996fdaa622ab33d0c88 VNC on this machine however gives screen ok so it seems like issue is close to drm(?) As mesa from few weeks earlier works ok on this machine - i suspect this might be regression?
<robmur01> hmm, that looks a lot like linear scanout of a tiled format. Possibly related to the recent modifier stuff?
<daniels> warpme_: which client is that running?
<warpme_> mythtv redering UI via GLES3
<warpme_> and zorg 1.20.8
<warpme_> zorg->xorg
<daniels> ah, X ...
<macc24> is segmentation fault when playing newest supertuxkart expected?
<macc24> mali t760mp4, mesa 20.1.6
<daniels> macc24: nope
<daniels> er, actually, it might be the assert fixed in master? I didn't think that had crept into stable but maybe it has
<daniels> do you have a backtrace?
<macc24> how to get backtrace?
<macc24> i just saw "Segmentation fault"
<daniels> try 'ulimit -c unlimited' to get a core dump, then gdb $(which supertuxkart) core, then type 'bt' at the prompt
<daniels> (or if you're just running under Wayland or something rather than directly on KMS, you can just run 'gdb supertuxkart')
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #panfrost
<robmur01> daniels: you mean not everyone runs native KMS stuff via SSH from another machine? :O
* macc24 hides VNC
* robmur01 has pretty much forgotten how to use computers "properly" by this point
<tomeu> macc24: doesn't seem to be related to panfrost
<tomeu> macc24: one would need to see what CallSystemFunctionNative does
<tomeu> it's maybe trying to call a NULL func pointer?
<daniels> robmur01: heh
<HdkR> Null function pointer would show up in backtrace
<HdkR> tomeu: Expectation is that getting an ARM board setup with the latest kernel will be the hard bit for me :P
<alyssa> endrift: wonderful
<alyssa> icecream95: sure :)
<alyssa> warpme_: right, that definitely looks like modifiers got botched
<alyssa> I'm unsure why that would affect T720 but not T860
<alyssa> ^ If that makes the issue go away, we can confirm it's modifiers, but that doesn't tell us why.
<warpme_> alyssa: perfect. pls give me some minutes as i'm in middle rebuilding with 5.8.5 kernel (report was from 5.9.rc3). builder should finish in 20-30min....
<alyssa> sure
<HdkR> Hmmm, I have a rockpro64 somewhere around here I Think
<HdkR> alyssa: Is the rockpro64 I have here one you have access to?
<alyssa> HdkR: Yeah
<alyssa> currently with kbase on it, I'd appreciate if that one stayed as currently configured
<alyssa> something something I tried to send you a rp64 already but nope ;P
<HdkR> :)
<HdkR> Time to order another one
<alyssa> what for?
<HdkR> I want to do Panfrost x86-64 testing and it seems like the best choice
<HdkR> Bifrost isn't yet at GL 3.x as far as I'm aware :P
<alyssa> HdkR: Sadly no :p
<HdkR> Ordered another one plus a couple of cases so I can glue the two boards together to live forever together
<HdkR> I need to clean up my SBC shelf. It's a huge mess
<warpme_> alyssa: with this patch app seems to be hanging. screen is black. i see xorg server started (no errors) - but app. is hanging
<robmur01> if only Atom C3-3445 devices actually existed... plenty of ASUS ZenPads for potential x86-Lima shenanigans, but no lovely T720s for x86-Panfrost :(
<alyssa> warpme_: ....uh
<HdkR> robmur01: It's more sane to keep the kernel space ARM and let the userspace play in the x86 pool anyway ;)
nlhowell has joined #panfrost
<alyssa> bbrezillon: I'm noticing some serious flushes on manhattan, wondering if we need to batch harder
camus1 has joined #panfrost
kaspter has quit [Ping timeout: 240 seconds]
camus1 is now known as kaspter
nlhowell has quit [Quit: WeeChat 2.9]
<bbrezillon> alyssa: do you know what causes those flushes?
<bbrezillon> clears maybe?
<alyssa> bbrezillon: finding out now
Green has quit [Ping timeout: 256 seconds]
nlhowell has joined #panfrost
<alyssa> looks like bad AFBC logic isn't helping
<alyssa> oh, interesting, entirely caused by the AFBC flushes
<alyssa> (no flushes if I disable AFBC)
<alyssa> so that's entirely my fault, ignore me
<alyssa> okay, right -- mh doesn't actually read from AFBC textures, but it still hits the stupid flush to find out if it needs to
<alyssa> AFBC does bring up some 'interesting' questions ;-;
<HdkR> :)
<HdkR> Compression is always fun
<HdkR> Just make every hardware block compression aware. Easy right? </s>
<alyssa> =)
<alyssa> uhhh
Green has joined #panfrost
nhp_ has quit [Ping timeout: 244 seconds]
nhp has joined #panfrost
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #panfrost
guillaume_g has quit [Quit: Konversation terminated!]
Green has quit [Ping timeout: 240 seconds]
Green has joined #panfrost
nlhowell has quit [*.net *.split]
leper` has quit [*.net *.split]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #panfrost
nlhowell has joined #panfrost
leper` has joined #panfrost
Green has quit [Ping timeout: 246 seconds]
Green has joined #panfrost
raster has quit [Quit: Gettin' stinky!]
raster has joined #panfrost
davidlt has quit [Ping timeout: 260 seconds]
rak-zero has joined #panfrost
raster has quit [Quit: Gettin' stinky!]
raster has joined #panfrost
buzzmarshall has joined #panfrost
raster has quit [Quit: Gettin' stinky!]
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #panfrost
_whitelogger has joined #panfrost
rcf has quit [Quit: WeeChat 2.7]
rcf has joined #panfrost
rcf has quit [Client Quit]
rcf has joined #panfrost
Ntemis has joined #panfrost
yann has quit [Ping timeout: 256 seconds]
stikonas has quit [Remote host closed the connection]