ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
hexdump02 has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
cnxsoft has quit [Read error: Connection reset by peer]
dsimic is now known as Guest11381
dsimic has joined #linux-sunxi
Guest11381 has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
Daanct12 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-sunxi
Daanct12 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
freemangordon1 has joined #linux-sunxi
apritzel has joined #linux-sunxi
ungeskriptet_ has joined #linux-sunxi
junari has joined #linux-sunxi
freemangordon has quit [Ping timeout: 480 seconds]
<junari> When I run some task, it may hit a weak core and sometimes a more powerful core. Because of this, the performance is different. I found the capacity-dmips-mhz parameter, but it doesn't seem to work for me
<junari> for example, little core: 42600497152 bytes (43 GB, 40 GiB) copied, 11.1165 s, 3.8 GB/s
ungeskriptet has quit [Ping timeout: 480 seconds]
<junari> big core 67492642816 bytes (67 GB, 63 GiB) copied, 11.4469 s, 5.9 GB/s
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #linux-sunxi
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-sunxi
Robot_ has joined #linux-sunxi
<junari> Looks like I forgot to save the changes and the capacity-dmips-mhz parameter is actually working
Robot_ has quit [Remote host closed the connection]
<jernej> junari: that's for A523?
<junari> jernej: yes
<jernej> so you have DVFS fully worked out?
apritzel has quit [Ping timeout: 480 seconds]
<junari> so far I've only tested performance mode
<jernej> I guess my question is more like if you figured out DSU/CPU clocks?
<jernej> e.g. write driver for it
<junari> Yes, but it quick backport from BSP
<jernej> that's ok, there are AW BSP drivers which were cleaned up for upstream
<jernej> I'm just trying to understand where we are with A523 support
<jernej> so I guess I can soon start to look into display support :) I believe it's very similar to H616, which needs to be solved beforehand.
<junari> Yeah, I think that would be a good starting point for driver development to send it to upstream
<junari> I also have some work in progress on temperature sensors. There are still some confusing aspects, but it somehow works
<junari> I'll be looking forward to your HDMI work :D
gsz has joined #linux-sunxi
<junari> Hmm, looks like running processes are not switching to higher performance cores. Still randomly
apritzel has joined #linux-sunxi
junari has quit [Remote host closed the connection]
junari has joined #linux-sunxi
<loki666> i'll try with a longer timeout
<loki666> ah no that was already with 1500
<apritzel> loki666: yeah, tbh the timeout is already very generous (actually far too long for a busy loop), so I doubt it's that, but wanted to rule that out
<apritzel> junari: the new BSP clock drivers are quite close to mainline (for a change), so it's absolutely fine to copy in this case
<apritzel> junari: they of course need some adjustments
<apritzel> was what that benchmark you showed, some kind of memcpy?
<junari> apritzel: it's dd if=/dev/zero of=/dev/null bs=1M count=10000
<apritzel> so I guess that's purely CPU frequency then?
<apritzel> well, must be, there is probably no difference otherwise ;-)
<apritzel> junari: that's on some H728 board, right? I find it quite odd that the slow cluster is only 1 GHz there, On the other packages it's always 1.4GHz
<junari> Yes, the speed difference is due to the task hitting different cores
<junari> It is x96qpro+ and these are the frequencies I got when I booted into android operating system
<apritzel> ah, I see, that's where I got the 1GHz for the slow cluster from as well
<junari> But I'm already in the process of overclocking
<apritzel> but the capacity-dmips-mhz is somewhat pointless, right, because it's the same for all eight cores, given they are all the same microarchitecture (same core even)
Schimsalabim has quit [Ping timeout: 480 seconds]
<junari> I did a run of 7z b at different frequencies and added opi-zero3 to the comparison https://gist.github.com/iuncuim/a2748d7d020ac60b4bf9e54d3d0030a8
Schimsalabim has joined #linux-sunxi
<loki666> apritzel: what's the next move then ? Seems like there was no ongoing operation since cmdr is 0x0...
<loki666> So it looks like the current operation never complete
<loki666> Its always with clock disable
<junari> loki666: do you know of any other upcoming consoles on the a527 besides gamemt e6 max?
<loki666> junari: a guy contacted me to send me a device... not received it yet, and no idea which console it's going to be
<loki666> don't think it' even shipped yet
<junari> I think this processor will be in demand in these kinds of devices. Since it can emulate psp with x2-x3 resolution in heavy games quite easily
<loki666> maybe the Helegaly K560... don't know
<loki666> ah no
warpme has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-sunxi
Daanct12 has quit []
Daanct12 has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
ftg has joined #linux-sunxi
ungeskriptet_ has joined #linux-sunxi
ungeskriptet__ has joined #linux-sunxi
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ has quit [Ping timeout: 480 seconds]
igraltist has quit [Remote host closed the connection]
igraltist has joined #linux-sunxi
ungeskriptet has joined #linux-sunxi
ungeskriptet__ has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]
Daanct12 has quit [Quit: WeeChat 4.5.2]
warpme has quit []
evgeny_boger has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 480 seconds]
junari has quit [Remote host closed the connection]
evgeny_boger has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<loki666> apritzel: about the mmc2 issue... I was wondering why it happens en mmc2 and not mmc2, could it be because vmmc-supply is GPIO controlled regulator which has a latency?
<loki666> It also always happens right when I insert the card
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
warpme has quit []
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7609-afed1336e, build type: debug, sources date: 20160102, built on: 2024-12-18 20:43:05 UTC 5.2.6+git-7609-]
gsz has joined #linux-sunxi
apritzel has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]