Ntemis has quit [Read error: Connection reset by peer]
vstehle has quit [Ping timeout: 240 seconds]
stikonas has quit [Remote host closed the connection]
kaspter has joined #panfrost
kaspter has quit [Remote host closed the connection]
kaspter has joined #panfrost
kinkinkijkin has quit [Ping timeout: 244 seconds]
buzzmarshall has quit [Remote host closed the connection]
kinkinkijkin has joined #panfrost
<icecream95>
Looks like phoronix is paying attention to things...
vstehle has joined #panfrost
kaspter has quit [Ping timeout: 262 seconds]
kaspter has joined #panfrost
<endrift>
Phoronix is great at paying attention to things
<endrift>
Larabel is less good at understanding what those things he's paying attention to actually mean though
<endrift>
I guess that's what happens when you're the only author on phoronix and have your thumbs in like 200 different pies at once though
<endrift>
polydactyl journalism
<HdkR>
I also love pie
<endrift>
I'm pretty out of it and despite the fact that I've seen the "avoiding X is a huge feature" quote dozens of times by now I somehow today blanked on the fact that X isn't being used as a standin for what was actually being discussed. Literally X Window System.
<HdkR>
X, For those times when Y isn't good enough
<endrift>
Didn't someone make a "Y Window System" one time, but it was just some weird garbage on top of SDL that didn't actually do anything valuable
<endrift>
I tried finding info about this recently and couldn't find it
<HdkR>
One could says that it was the Whhhhhyyy?! window system
<alyssa>
endrift: what the anti-Waylanders forget is Wayland is pushed by the same people who historically have hacked on X :)
yann has quit [Ping timeout: 240 seconds]
nlhowell has quit [Ping timeout: 260 seconds]
<icecream95>
alyssa: Is that a feature or a bug?
<alyssa>
icecream95: Bug, definitely a bug ;P
camus has joined #panfrost
kaspter has quit [Ping timeout: 260 seconds]
camus is now known as kaspter
tgall_fo_ has joined #panfrost
tgall_foo has quit [Ping timeout: 240 seconds]
<alyssa>
icecream95: re job_barrier, it's a different bit but I'm not sure if job_barrier implies it
icecream95 has quit [Quit: leaving]
<daniels>
alyssa: yeah ... we learned from the experience and are applying those lessons to produce the best possible window system. or we're the same idiots making the same mistakes again just greenfield. or we have so much PTSD that we've run too far away from X11 and now we're making the polar opposite mistakes. choose your adventure :)
davidlt has joined #panfrost
<alyssa>
>:)
<macc24>
daniels: as long as my windows don't lag i'm fine :p
<urjaman>
hmm... this might be Xorg or the rockchip DRM driver too, but i feel like the location of the mouse cursor overlay gets updated one frame late on my C201 ... i wouldn't notice (i mean, it only moves very little normally) but kicad can move it in chunks with the arrow keys and it moves one move late
<urjaman>
like i think the hardware cursor isn't panfrost at all but i just thought to mention it here because ... this is funky :P
<macc24>
urjaman: how did you get xorg to not lag?
kaspter has quit [Read error: Connection reset by peer]
camus has joined #panfrost
<macc24>
all i could get on modesetting driver was slower than fbdev
<urjaman>
i didn't do anything special (i tried to help you already before lol)
<macc24>
lol
camus is now known as kaspter
<urjaman>
technically on 2D only (glamor off, no hw accel) yeah modesetting is slower than fbturbo or such, but with glamor enabled it's okay (tho if you're playing video other 2D things might happen hilariously late... priorities?. but never had the laggy windows type problems you described)
<urjaman>
oh btw i tried to add the voltage control (devfreq whatever) patches to 5.9 but it had no effect to how FAULT-y my attempt of running that kernel was, so I just had enough for that attempt and just booted my 5.4 again
<macc24>
i have linux 5.8.9 working if that matters
<urjaman>
yeah anything > 5.4 doesn't work right on my C201
<urjaman>
maybe i could try building that drm-next branch i pulled the patches out of (i was expecting them to be in 5.9, but nope)
<urjaman>
(one of the "wtf is up with that" changes in 5.9 is sbs_battery spewing a complaint about it not recognizing the chemistry of the battery... but that didn't cause a problem running it, and the gauge seemed to report the percentage right too...)
<urjaman>
basically i could get it to a desktop, but very quickly after that things just ... graphically hang to a stop because GPU faults and timeouts
<macc24>
did you include vkms driver?
<urjaman>
... what?
<macc24>
in some linux version they added this
<macc24>
and it broke sway for me
<urjaman>
(i used basically the same config i did with 5.4, just answered something sensibleish to the questions make oldconfig asked... but i don't remember that)
<urjaman>
the answer is no (ssh'd into the C201, and opened up a make menuconfig)
<urjaman>
but yeah my attempt was a couple weeks ago, based on it being rc3 (now is rc5) ... maybe i should take a second look
<macc24>
git bisect?
<macc24>
but at this point i don't know
<urjaman>
that'd be kinda silly for an already known problem
<macc24>
that's the 'i don't know' part
<urjaman>
(5.5 broke voltage scaling... i just dunno why the patches didn't fix it)
<urjaman>
but yeah should maybe debug it, see if it's doing the thing or if i have some config wrong
<urjaman>
(i'll admit that it does annoy me that kernel folks are like "yeah we broke a bunch of hardware doing this new thing" ... and not fix it for 5 releases)
<macc24>
"We do not regress" ~Linus
<robmur01>
strictly it's "we don't regress *userspace*", and in the context of deliberate changes ;)
<robmur01>
inadvertently breaking hardware unfortunately happens a lot
<robmur01>
but the whole point of free software is that you can fix it yourself :P
<urjaman>
another thing with 5.9... the broadcom wlan is working ... well, it wasn't working well to start with, but this can be qualified as not really usefully working (it takes forever to connect, networkmanager keeps messing about with it, DNS queries fail... but like i did make an ssh connection to the machine...)
<urjaman>
and then the GPU fails
<urjaman>
switched to my realtek USB wlan, commanded the devfreq governor on the GPU to performance, and the debug filesystem atleast claims that the gpu regulator jumped to max frequency
<urjaman>
i still got a spew of gpu failts when i opened my xfce terminal tho... but the system is still graphically running (so far), i'm typing this from said terminal
<urjaman>
*max voltage ...
<alyssa>
robmur01: It's fine if the hw regresses since hw isn't userspace, obviously.
<urjaman>
http://ix.io/2xTe <- this is the fault spew i got from opening a terminal for the first time... it still mostly seems to work tho
<urjaman>
hmm switched back to the ondemand governor for the gpu and it seems to be doing the job ok... so the remaining questions are whats up with the broadcom driver (and i think using it hangs some workers or workqueues and after that the kernel is a bit f'ed up), and what are those gpu faults then if it's not voltage related...
<robmur01>
urjaman: that can still happen when jobs are killed and BOs disappear before the GPU has stopped
<robmur01>
slower GPUs make it more likely... incidentally now I've got my FPGA back for 40MHZ MP1 fun :D
<robmur01>
I've got Boris' "MMU context lifetime" patch but I don't think it's entirely solved the issue (or I've bodged rebasing it...)
<urjaman>
hmm, who decides on the default positions for multiple displays when they initially appear? like on my PC something decides to put them somewhat logically side-by-side when xorg starts (just login manager running)...
<urjaman>
but on the C201 it decides that they should both be at 0.0, just differently sized
<urjaman>
is it the rockchip DRM driver?
<urjaman>
i can ofc use xrandr or XFCE to move them but still... what
<urjaman>
i mean... i guess being at zero is kinda just ... it didn't think about it, at all, not really a decision but still
dstzd has quit [Client Quit]
dstzd has joined #panfrost
jernej has quit [Client Quit]
<urjaman>
robmur01: got a link for said patch? (i could look into stuffing it to my pile of patches, if it works for 5.9 ... tho the weird thing is i don't remember these faults on 5.4)
jernej has joined #panfrost
jernej has quit [Client Quit]
jernej has joined #panfrost
<urjaman>
on a positive (or atleast neutral) note, the cursor being late thing doesn't seem to be happening on 5.9, atleast right now... i dunno if it needs more running/things to happen before it happens
<urjaman>
and i seem to have integrated my HDMI patches okay, or atleast i didn't break a 1080p display (should still try out my 1920x1200 too just to be sure :P)
<urjaman>
okay that patch is ... nontrivial for me to apply to my 5.9
jernej has quit [Client Quit]
jernej has joined #panfrost
<urjaman>
okay that's how long the 5.9 ran ... i opened up a youtube video, and attempted to move the video to the external display and the audio kept going but the whole desktop just hung...
<urjaman>
it still talks over ssh, so yeah a couple of translation faults and job timeouts in there... but dunno why it's just frozen now
yann has joined #panfrost
<urjaman>
http://ix.io/2xTA even the kernel now agrees that something hung, but i'm not smart enough to understand what's up from that backlog (something something fences? what?)
davidlt has quit [Ping timeout: 260 seconds]
<robmur01>
looks like that fence is never going to get signalled, so it'll be waiting for a long time
<urjaman>
okay some of those faults do happen on 5.4 too when starting things up, it had just been so long since i last ran dmesg after boot on 5.4 that i'd forgotten (and over time it gets spammed with elan_i2c messages so...)
camus has joined #panfrost
kaspter has quit [Remote host closed the connection]