Jookia has quit [Remote host closed the connection]
Jookia has joined #linux-sunxi
gsz has joined #linux-sunxi
AntoniAloyTorrens[m]1 has quit []
MatrixTravelerbot[m] has quit []
paulk-bis has joined #linux-sunxi
paulk has quit [Read error: Connection reset by peer]
psydroid[m] has quit []
aedancullen has quit []
kjn260 has quit [Read error: Connection reset by peer]
gsz has quit [Ping timeout: 480 seconds]
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-sunxi
KREYREN has quit []
cch_ has quit [Ping timeout: 480 seconds]
cch has joined #linux-sunxi
cmeerw[m] has quit []
ftg has quit [Read error: Connection reset by peer]
dickenhobelix[m] has quit []
exkc has quit []
exkcmoeadmin[m] has quit []
JohnDoe_71Rus has joined #linux-sunxi
paulk has joined #linux-sunxi
paulk-bis has quit [Read error: Connection reset by peer]
kjn260 has joined #linux-sunxi
Tooniis[m] has quit []
junari has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
obbardc has quit []
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.4, revision: 5.2.4+git-7587-04f93acf5, build type: debug, sources date: 20160102, built on: 2024-06-02 21:46:49 UTC 5.2.4+git-7587-]
apritzel has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<junari>
Have anyone found a fix for the schedutil and h616 cpufreq?
montjoie_ has joined #linux-sunxi
montjoie has quit [Ping timeout: 480 seconds]
<tokyovigilante>
I have not regrettably, one of the CFW groups I'm in is experimenting with ondemand with some tuning, but interestingly schedutil works on the vendor BSP for the H700 at least, so must be a bug somewhere. loki666 posted that it wasn't working on the ML but no feedback yet
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
<junari>
Yes, it doesn’t work for me either, neither with kernel 6.6 nor with 6.9
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
junari has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-sunxi
gnarface has quit [Read error: Connection reset by peer]
gnarface has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit []
gnarface has quit [Quit: Leaving]
tlwoerner has quit [Ping timeout: 480 seconds]
gnarface has joined #linux-sunxi
gsz has joined #linux-sunxi
Robot_ has joined #linux-sunxi
<Robot_>
does anyone have experience with t113-S4 (m4020dc0) chips? I have bought some, replaced on T113-s3 board, and ddr init code from xfel fails.
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
apritzel has joined #linux-sunxi
<apritzel>
Robot_: did you try mainline U-Boot?
<Robot_>
i wanted to try just low level stuff first
<apritzel>
Robot_: well, I don't know much about the quality of the xfel DRAM code, but we spent quite some time to make the U-Boot DRAM code more robust
<Robot_>
xfel code is the payload from allwinner, but my chip has fuse set to 0xa, so this patch is relevant
<Robot_>
i will try to patch the payload manually, and then try uboot
<apritzel>
Robot_: in U-Boot we have some DRAM parameters, for the joint D1/T113 DRAM init code, so I wonder if those parameters are different between T113-s3 and T113-s4
<apritzel>
not sure how AW gets away with no parameters, is the DRAM code T113 only? I'd guess with co-packaged DRAM the parameters are the same at least for every T113-s3
<Robot_>
xfel has parameters, it loads the DDR payload, and loads different parameter table into the payload at fixed offset
<Robot_>
only difference in t113-s3 and s4 is the clock frequency, width and rank are autoprobed
<Robot_>
apritzel: after patching the payload from xfel, i am able to bring up DDR in t113-s4
<apritzel>
xfel has parameters> ah, didn't know
<apritzel>
so my T113-s3 (on a MangoPi MQ-R) reads 0xa in that fuse, let me check how it behaves with that patch ....
<Robot_>
it doesnt boot
<Robot_>
i just tried with mangopi
<Robot_>
both t113-s3 and t113-s4 chips have fuse set to 0xa
<Robot_>
but need different remapping
<apritzel>
right: DRAM:ERROR: auto scan dram rank & width failed
<Robot_>
yay, china :) ....
<apritzel>
so this more a s3 vs s4 differentiator than a wrong value then
<Robot_>
can we differenciate between these two chips ?
<apritzel>
that was just my next question as well ;-)
<apritzel>
I guess the SID ID in the first word differs
<apritzel>
so for my T113-s3 it's 0x93406000 (at address 0x03006200)
<Robot_>
mango pi : 93406000 ac004814 01440821 60721f8b