<Lyude>
alyssa: is glmark-es2 causing the oom killer to go off normal for panfrost?
<Lyude>
like; less then a couple seconds into running it
_whitelogger has joined #panfrost
<alyssa>
Lyude: explain re the packed?
<alyssa>
and yes probably, sorry :P
<Lyude>
alyssa: we probably don't actually need the __attribute__((packed)) all over the place in mali-ioctl.h, which is a bit silly since I added them there <<
<Lyude>
but either way that'd be gotten rid of going to the kbase headers
<alyssa>
ah
<Lyude>
alyssa: well I see it allocating stuff in the mali debugfs
belgin has quit [Remote host closed the connection]
Lyude has quit [Quit: WeeChat 2.2]
Lyude has joined #panfrost
<HdkR>
alyssa_: The Pixel C did the same thing though :P
yawniek has joined #panfrost
<yawniek>
quick question since i stumbled over panfrost in #sway . is it already capable of running something like sway on a rockpro64 board and doing basic stuff such as displaying images/browser?
<HdkR>
alyssa_: Still doing the winsys hack thing right? :)
<Lyude>
yawniek: not yet
<Lyude>
HdkR: yeah-we still are
<Lyude>
I wouldn't mind working on a proper winsys with the arm kernel driver for the time being- assuming it isn't more effort then just writing the new kernel module + winsys
<Lyude>
after I get it to actually render on this board and fix the lack of resource freeing
pH5 has quit [Quit: -_-]
<alyssa_>
HdkR: mmf
<alyssa_>
yawniek: Unfortunately not yet, but we're getting there :)
<Lyude>
yessss
<Lyude>
an error!
<Lyude>
es2_gears does seem to be a much better candidate for testing this
<Lyude>
(also i'm fixing it not being in egl-utils in fedora :)
<HdkR>
Whoa. Was the package so old in fedora that it never had es2_gears?
<Lyude>
HdkR: no-it was just that I was searching for es2gears in the wrong spot with `dnf provides` :p, but also it's in mesa-demos and seeing as es2_info isn't there and is in egl-utils, I'm assuming it's probably a mistake es2_gears isn't there
<Lyude>
(as glxinfo has glxgears and both are in glx-utils)
<HdkR>
ah
<Lyude>
[66194.120791] mali mali.0: GPU Fault 0x00000088 (SHAREABILITY_FAULT) at 0x0000008518f22ee0
<Lyude>
(gonna figure out what that means, but figured i'd put it here in case anyone already knows)
<Lyude>
assuming it's just a perms error with resource allocation
<alyssa_>
SHAREABILITY_FAULT? that's a new one, lol
<alyssa_>
Lyude: morged
<alyssa_>
not sure why I didn't get an email for it
<Lyude>
alyssa_: new kernel module, new errors :)
<alyssa_>
:D
<Lyude>
also; have you tried getting the latest kbase module compiled on your chromebook to see if it works?
<alyssa_>
Haven't had time
<Lyude>
alyssa_: mind giving it a shot the next chance you get?
<Lyude>
i do wanna merge this in master at some point (not yet, obv)
<alyssa_>
It's... kind of a bigger project than it sounds like. I'm sorry
<yawniek>
ok thanks. if working will it be possible to output 3840 × 2160 on a rockpro64? (i have a panel+controller here that i'd like to use to display pictures)
<alyssa_>
yawniek: ...does the _blob_ even work at that resolution? :P
<Lyude>
alyssa_: i mean; i can help you do it if you need. i've got it building just fine here, and if you grabbed me the source url for whatever chromeos kernel your machine uses (I may have asked for this already and forgotten) I wouldn't mind testing it out there myself
<Lyude>
yawniek: i mean, the plan is if the hw can do it then the hw will do it :)
<Lyude>
so yeah, what alyssa_ said
<yawniek>
the wiki says Digital Video output up to 4K@60Hz. however from what i read i isnt possible in X but only for videos
<alyssa_>
Hm
<yawniek>
and that 4k is a lie anyway, its probably UHD
<alyssa_>
Lemme check something
<Lyude>
yawniek: i mean the X blob is really awful
<Lyude>
like, it's really really awful
<Lyude>
so that's moreso a limit of their blob then anything
<alyssa_>
yawniek: The RK3399 datasheet suggests the chip is capped at 2560x1600 (in display hardware)
<yawniek>
its not important, i just wondered if its worth getting that board
<yawniek>
alyssa_: ok thanks, that answers the question then. i wonder why they advertise it as 4k capable then
<alyssa_>
I'm not sure
<alyssa_>
yawniek: Ahhh, nvm, the HDMI interface can do 4k
<alyssa_>
Max resolution is actually 4096x2160
<alyssa_>
I had somehow concluded you meant DSI
<alyssa_>
So if it's HDMI input it should work, otherwise prolly no?
<alyssa_>
...or 4k can also go over DP?
<alyssa_>
This is confusing as heck
<alyssa_>
Sorry that was vague
<yawniek>
yeah on hdmi
<alyssa_>
I'm just going off the public datasheet and.. yeah
<yawniek>
or maybe eDP
<HdkR>
Yea, RK has supported 4k since 3288. 3399 should support it as well. Just depends on the interface :P