narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
vagrantc has joined #linux-amlogic
montjoie has quit [Ping timeout: 255 seconds]
montjoie has joined #linux-amlogic
camus has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
hexdump0815 has quit [Ping timeout: 246 seconds]
hexdump0815 has joined #linux-amlogic
f11f12 has joined #linux-amlogic
JohnnyonFlame has quit [Read error: Connection reset by peer]
jacobk has quit [Ping timeout: 246 seconds]
luka177 has quit [Ping timeout: 255 seconds]
ldevulder has joined #linux-amlogic
<rockosov> narmstrong: xdarklight jbrunet Hello Neil, Martin and Jerome! I hope you're doing well! Could you please take a look at this series: https://lore.kernel.org/all/20230823213630.12936-1-ddrokosov@sberdevices.ru/? Is everything okay, or is there something that needs to be fixed? Should I wait for the next merge window?
mripard has joined #linux-amlogic
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 245 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
adema has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
adema has joined #linux-amlogic
mripard has quit [Quit: mripard]
mripard has joined #linux-amlogic
naoki has quit [Quit: naoki]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 245 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 245 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
jacobk has joined #linux-amlogic
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
f11f12 has quit [Quit: Leaving]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 246 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 250 seconds]
jacobk has quit [Ping timeout: 258 seconds]
jacobk has joined #linux-amlogic
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 246 seconds]
mripard has quit [Remote host closed the connection]
f_ has joined #linux-amlogic
<f_> hi
f_[xmpp] has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
<f_> let's continue......rewriting stuff
<f_> I won't stop until U-Boot SPL succeeds at relocating its stack :)
<Kwiboo> f_: Hi, hehe, I hope you can make it work :-)
<Kwiboo> I am trying to dig some more into why I need the change ushort into uint on mmc_cmd struct, will try some more different gcc versions to see if the issue is related to my env, an issue with optimization done by gcc, or a cpu/cache issue
<f_> Hope we can make it work!
<f_> Kwiboo: yeah that change looks unnecessary unless you have a b0rked compiler
zkrx has quit [Ping timeout: 260 seconds]
<Kwiboo> Yeah, something is very strange, looking at assembly everything looks fine on calling site: mov w0,#0x33; ... strh w0,[sp, #cmd]; ... mov w0,#0x8; ... str w0,[sp, #blocksize]
<Kwiboo> but possible wrong value is picked up from stack at called function side
<f_> Could be the stack having issues ¯\_(ツ)_/¯
<f_> in that case we could use the stack address Amlogic BL2 uses
<f_> (sometimes Ghidra is really useful even if you have sources)
<Kwiboo> the value for blocksize, 8, seem to get used as cmdidx, 51, and I have noticed similar for similar part when I tried to force to use cmd 51 when the function was called with cmd 8
<Kwiboo> Yeah, tried to look at the code in Ghidra, one bad version (ushort) an a working version (uint), but optimization has it working differently, so not a good compare
<Kwiboo> will try to find a different compiler version that works with ushort
<f_> The compiler optimises for size IIRC
<f_> (unless you changed -Os to something else)
<Kwiboo> yeah, should be optimized for size, using default options
<Kwiboo> also think adding a mb() helped at one point, but need to re-test that theory
<Kwiboo> also had same issue on my sm1 board, so I do not think it is cpu issue, probably broken compiler
<f_> Perhaps.
gis has quit [Ping timeout: 244 seconds]
GNUtoo has joined #linux-amlogic
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 245 seconds]
gis has joined #linux-amlogic
<f_> $ aarch64-linux-gnu-gcc --version
<f_> aarch64-linux-gnu-gcc (GCC) 13.1.0
<f_> ^ Kwiboo
f_ has quit [Ping timeout: 250 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 246 seconds]
jacobk has joined #linux-amlogic
mturquette_ has joined #linux-amlogic
cyrozap_ has joined #linux-amlogic
mturquette has quit [Ping timeout: 246 seconds]
mturquette_ is now known as mturquette
jelly has quit [Ping timeout: 246 seconds]
cyrozap has quit [Ping timeout: 246 seconds]
tsegers has quit [Write error: Connection reset by peer]
tsegers has joined #linux-amlogic
<Kwiboo> f_: Have tested multiple gcc versions now, from 8.4.0-3ubuntu1 up to 13.1.0-2ubuntu2~23.04, and I get same issue with all of them
<Kwiboo> Only thing that have helped so far, is 1. ushort -> uint, 2. mb() between cmd. and data. assignments, 3. set data. values before cmd. values
jelly has joined #linux-amlogic
luka177 has joined #linux-amlogic
rockosov has quit [Ping timeout: 246 seconds]
JerryXiao has quit [Ping timeout: 246 seconds]
rockosov has joined #linux-amlogic
JerryXiao has joined #linux-amlogic