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
karolherbst has quit [Ping timeout: 272 seconds]
karolherbst has joined #panfrost
abordado_ has joined #panfrost
abordado_ has quit [Remote host closed the connection]
Ixnus has joined #panfrost
<Ixnus> Hello, which gpus, panfrost currently supports ? Is there such a list somewhere ? I will read the irclog later. Thanks.
<HdkR> Those are supported, Any midgard outside of that list may or may not work
<Ixnus> thank you!
Ixnus has quit [Remote host closed the connection]
stikonas has quit [Remote host closed the connection]
Stary has quit [Quit: ZNC - http://znc.in]
vstehle has quit [Ping timeout: 258 seconds]
Stary has joined #panfrost
NeuroScr has quit [Quit: NeuroScr]
adjtm has quit [Ping timeout: 240 seconds]
megi has quit [Ping timeout: 272 seconds]
icecream95 has joined #panfrost
nerdboy has quit [Ping timeout: 260 seconds]
icecrea105 has joined #panfrost
icecream95 has quit [Ping timeout: 265 seconds]
icecream95 has joined #panfrost
icecrea105 has quit [Ping timeout: 265 seconds]
buzzmarshall has quit [Remote host closed the connection]
davidlt has joined #panfrost
karolherbst has quit [Ping timeout: 255 seconds]
enunes has quit [Ping timeout: 260 seconds]
karolherbst has joined #panfrost
enunes has joined #panfrost
vstehle has joined #panfrost
tgall_foo has quit [Read error: Connection reset by peer]
<tomeu> robmur01: got to reproduce the random failures while watching the frequency, and indeed it starts going wrong after a switch to the highest freq
adjtm has joined #panfrost
guillaume_g has joined #panfrost
gcl_ has quit [Ping timeout: 240 seconds]
pH5 has joined #panfrost
gcl has joined #panfrost
alpernebbi has joined #panfrost
kaspter has joined #panfrost
gcl_ has joined #panfrost
gcl has quit [Ping timeout: 255 seconds]
yann has quit [Ping timeout: 258 seconds]
karolherbst has quit [Remote host closed the connection]
karolherbst has joined #panfrost
icecream95 has quit [Ping timeout: 265 seconds]
alpernebbi has quit [Quit: alpernebbi]
yann has joined #panfrost
_whitelogger has joined #panfrost
megi has joined #panfrost
nlhowell has joined #panfrost
kaspter has quit [Ping timeout: 260 seconds]
<nlhowell> i have the c201 rk3288-based chromebook, running linux-5.3.2 and mesa-20.0.0 with panfrost support
<nlhowell> and my X server detects, evidently, two displays, or two cards, I can't tell
<nlhowell> one of them it labels "0" so logs are prefixed with "modeset(0)"
<nlhowell> the other 'G0', logs are prefixed with "modeset(G0)"
<nlhowell> modeset(0) lines show glamor acceleration on panfrost, and DRI driver is listed as 'rockchip'
<nlhowell> and is associated with output eDP-1
<nlhowell> G0 is evidently some sort of virtual display, and doesn't get any acceleration afaict
<nlhowell> but I get what seems to me to be conflicting reports from glxinfo and glxinfo -B
<nlhowell> glxinfo -B says "panfrost" while glxinfo shows server vendor string "SGI" (software rendering, iiuc)
<nlhowell> glxinfo -B http://dpaste.com/2HXH6V1.txt
<nlhowell> verbose X log http://dpaste.com/2HFX51B.txt
<nlhowell> can anyone provide advice? should I be seeing "rockchip" selected as the dri driver?
davidlt has quit [Ping timeout: 265 seconds]
<tomeu> nlhowell: I think everything is fine regarding panfrost
<tomeu> you aren't getting acceleration on edp-1?
<nlhowell> if so, it isn't very fast
<nlhowell> 30fps on glxgears
<nlhowell> and there is e.g. noticable lag in rxvt-unicode when running top
<tomeu> nlhowell: what does "glxgears -info" say?
<nlhowell> aside from the framerate, it looks fine
<nlhowell> says panfrost is being used
<urjaman> the server glx vendor string is always SGI (i guess if you have modern Xorg atleast)
<urjaman> like even on my AMD graphics PC
<nlhowell> urjaman: ah, ok; thanks, I didn't know this
<nlhowell> so it seems, then, that everything is fine, except that performance seems pretty slow
<urjaman> i guess it's how every browser user agent is Mozilla :P
<nlhowell> :D
<urjaman> (similar to how...)
<robmur01> tomeu: I guess that's "good" in the sense that at least it's probably not some other *new* problem :)
<tomeu> robmur01: it's *very* good in that sense :)
<robmur01> if I can make the time I'll try to resurrect my first attempt at registering the regulators for a quick fix (and think about coming back to the bigger rework later)
<robmur01> (from what I saw, the whole API stinks)
<alyssa> nlhowell: if you could install perf and run `sudo perf top`, use the desktop doing something slow and screenshot that -- it might help?
JaceAlvejetti has quit [Ping timeout: 240 seconds]
JaceAlvejetti has joined #panfrost
<nlhowell> alyssa: ok, i will give it a go
<nlhowell> thanks!
nlhowell has quit [Read error: Connection reset by peer]
nlhowell has joined #panfrost
raster has joined #panfrost
<alyssa> :+1:
davidlt has joined #panfrost
tgall_foo has joined #panfrost
<nlhowell> i am not sure what to make of it
<nlhowell> rockchip_dri.so shows up in the list
<nlhowell> along with memory operations from libc
<nlhowell> it seems some spinlocks are the major offenders
<nlhowell> i tried to get some results from forcing urxvt to redraw, but i wasn't able to time it right
<robmur01> nlhowell: if you're feeling brave, it's usually possible to infer which locks time is being spent under by looking at the call chains for where the unlocks happen (perf record -g/perf report)
<alyssa> (Also, compiling mesa master might help. If nothing else, it'll get us symbols.)
<robmur01> although it's a pretty safe bet that it's mostly monkeying about with the pagetables under as_lock
* robmur01 contemplates digging out and reviving the RK3288 box for the sake of 32-bit kernel gubbins
<daniels> robmur01: should be pretty straightforward, the firefly + rock2-square boards have worked well with mainline since forever
<robmur01> daniels: yeah, I had it running mainline kernel + u-boot ~2 years ago, it's just not been powered up since
<robmur01> the only annoyance is that it has the weirdo RK1000 audio/video codec, which has no mainline driver and gets disconcertingly hot
mixfix41 has quit [Ping timeout: 252 seconds]
mixfix41_ has quit [Ping timeout: 265 seconds]
_whitelogger has joined #panfrost
raster has quit [Quit: Gettin' stinky!]
nlhowell has quit [Ping timeout: 240 seconds]
nlhowell has joined #panfrost
yann has quit [Ping timeout: 260 seconds]
pH5 has quit [Quit: bye]
pH5 has joined #panfrost
gcl_ has quit [Ping timeout: 255 seconds]
gcl has joined #panfrost
MastaG has quit [Quit: The Lounge - https://thelounge.chat]
MastaG has joined #panfrost
<xantoz> is anyone else having issues with firefox 73 on wayland (sway) when you have enabled OpenGL compositing? on mesa git 8f5a252d
<xantoz> downgrading mesa to 19.3.4 seems to have solved the issue for me
<xantoz> the issue being that the window contents never update unless I resize the window
<xantoz> it's just frozen, but keeps responding to clicks and key presses as you can see when you force an update by resizing the window
<xantoz> this is on manjaro for the pinebook pro if that matters
<xantoz> disabling opengl compositing also solved the problem of course, but using OpenGL compositing makes firefox quite a bit more snappy
mixfix41 has joined #panfrost
raster has joined #panfrost
yann has joined #panfrost
stikonas has joined #panfrost
davidlt has quit [Ping timeout: 240 seconds]
buzzmarshall has joined #panfrost
TheKit has joined #panfrost
gcl_ has joined #panfrost
gcl has quit [Ping timeout: 240 seconds]
NeuroScr has joined #panfrost
pH5 has quit [Quit: -_-]
NeuroScr has quit [Quit: NeuroScr]
_whitelogger has joined #panfrost
raster has quit [Quit: Gettin' stinky!]