<beerman>
jaeger guess it might break every now and then
<beerman>
I think jue wouldn't be a fan, but we can certainly discuss this
<beerman>
so, new kernel: no change in resolution. only one monitor: no change in resolution. i have no idea
<beerman>
i'd need to investigate the problem
<beerman>
Current mode: 1152x864 @ 75.000 Hz instead of fhd
<jaeger>
No strong feeling, just thinking about it
<beerman>
We can add that to the "to discuss"-list for 3.8
ukky has quit [Ping timeout: 240 seconds]
<pitillo>
here gcc is still on the way
<pitillo>
rpi3 performance is a big sheet... I don't knownwhat's happening, but that's not normal
ukky has joined #crux-arm
<beerman>
heh yeah i imagine this to be a real problem on these old platforms
<pitillo>
but I have the feeling that it's not related to the platform... it's something related to software
<pitillo>
it's really slow and on old release, it was a powerful device
<pitillo>
*releases
<beerman>
mh
<beerman>
this is with lto again right?
<beerman>
always takes longer with lto
<beerman>
i got an old intel nuc from 2015 today. not sure about the specs, just i3-6100u, but that might be neat for a few things
<jaeger>
I still use my old NUC as an HTPC... I think it's something like an i5-4250u... not super fast but decent
<pitillo>
beerman: that could be possible... may be I need to rebuild all without lto and test... 48h for gcx on the rpi3 is shame
<pitillo>
s/gcx/gcc
<pitillo>
I'll continue tomorrow... let's see if it ends soon
<beerman>
the nuc i am unsure off yet, really. its better than it going to waste
<beerman>
pitillo if its that bad, I guess you could disable it. luckily, gcc is one of these ports not rebuilt often. python is worse in that regard I think
<beerman>
i might have a thing or two I can do with it, its powerful enough for a lot of things really