lkcl has quit [Read error: Connection reset by peer]
<dddddd>
* The A64 chip cannot work without this regulator off, although
<dddddd>
* it seems to be only driving the AR100 core.
<dddddd>
* Maybe we don't still know well about CPUs domain.
<dddddd>
*/
<dddddd>
®_fldo2 {
<dddddd>
regulator-always-on;
<dddddd>
Is this some typo? cannot+without+off !?
<catphish>
if it's not, it a terrible choice of words :)
<dddddd>
Seen at several .dts at linux-4.20/arch/arm64/boot/dts/allwinner
<smaeul>
most likely copy and paste
<smaeul>
so if it was wrong at first...
<smaeul>
but I can tell you that 100% FLDO2 must be *on*
<catphish>
i can only imagine it means the regulator must be enabled
<smaeul>
so the comment is very wrong
<dddddd>
thanks!
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 250 seconds]
IgorPec has quit [Ping timeout: 258 seconds]
lurchi_ is now known as lurchi__
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 258 seconds]
LargePrime has quit [Ping timeout: 244 seconds]
scelestic has quit [Quit: leaving]
davidperrenoud has quit [Quit: Connection closed for inactivity]
scelestic has joined #linux-sunxi
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 244 seconds]
lurchi__ is now known as lurchi_
ninolein has joined #linux-sunxi
f0xx has quit [Ping timeout: 258 seconds]
<jernej>
hm... I had to revert a66d972465d15b1d89281258805eb8b47d66bd36 to run linux successfully on H6
<jernej>
I wonder if this is toolchain issue
<anarsoul>
try recompiling from scratch?
<anarsoul>
change itself looks perfectly fine to me
<anarsoul>
(and it works fine on A64)
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
gamelaster has joined #linux-sunxi
<jernej>
I rebuild multiple times today (cleanly)
<jernej>
and yes, it works for me for A64 too
<jernej>
so, there may be some memory issue
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 268 seconds]
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 250 seconds]
<martinayotte>
jernej: anarsoul: I've got issue too with H6 (OPiOne+/OPiLite2), I've used the afaerber defconfig, tweak it a bit, and it was working on H6.
BenG83 has quit [Read error: Connection reset by peer]
<jernej>
yes, it seems soo
<jernej>
what was your solution?
<martinayotte>
I've used the @afaerber defconfig, tweak it because build issue with AXP2xx, but then it pass, and working since 10 mins. The diff between both this defconfig and the one used in Armbian is soo huge, I don't find the reason why it is now working. I would prefer using your solution if it is the real reason ...
<jernej>
not sure what to do
<jernej>
if it solveable with config, I'm all for it
<jernej>
but if defconfig fails, that's wrong
<jernej>
@afaerber defconfig didn't work for me
Mr__Anderson has quit [Remote host closed the connection]
<martinayotte>
jernej: I found an issue, probably unrelated, python gpio produce "Operation not permitted", maybe due to CONFIG_IO_STRICT_DEVMEM=y in @afaerber defconfig
<jernej>
I doubt that's the reason, but I can try
<martinayotte>
Also, there is so many drivers enabled in @afaerber version, I would tend to avoid it, it take twice the time as usual to build ... ;-P
<jernej>
I have disabled "strict devmem", so it's not the reason
<martinayotte>
Right, but I mean about my issue gpio permissions ... I will try to remove it from this version.
megi has quit [Ping timeout: 244 seconds]
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 250 seconds]
<martinayotte>
CONFIG_IO_STRICT_DEVMEM doesn't even exist on any Kconfig 4.20.y, I don't know where it is coming from ... I will do a build as yours : reverting a66d972465d15b1d89281258805eb8b47d66bd36
t3st3r has quit [Remote host closed the connection]
t3st3r has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 245 seconds]
lurchi_ has joined #linux-sunxi
lkcl has joined #linux-sunxi
gamelaster has quit [Ping timeout: 258 seconds]
reinforce has quit [Quit: Leaving.]
<catphish>
in case this is useful information and i don't contribute it in a better way, i'll mention now - it's necessary to configure the writeback module's file scaling settings, even if the fine scaler is bypassed