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 - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
mag has quit [Quit: Bye]
mag has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 256 seconds]
cottsay has quit [Quit: TTFN]
cottsay has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
buzzmarshall has quit [Remote host closed the connection]
return0e has quit []
_whitelogger has joined #linux-amlogic
AUser has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
AUser has joined #linux-amlogic
yann has quit [Ping timeout: 258 seconds]
hexdump0815 has joined #linux-amlogic
<hexdump0815> xdarklight: i think the m8s box is simply broken - memtester shows reproducably errors and i then compiled a static memtester binary and ran it on android where it gave errors too - linux kernel cmdline memtest=64 did not help either - so bye bye m8s most probably ...
<hexdump0815> xdarklight: did you really push your mxiii usb fix yesterday? i could not find it
<xdarklight> hexdump0815: sad to see hardware go, I only had this once (for my GXBB board) but it also threw memory errors (so many that sometimes even u-boot wouldn't initialize)
<hexdump0815> xdarklight: i looked through the commit history of your latest branch, but was not able to see that commit and still cannot see it there ...
<xdarklight> hexdump0815: for me it's on the bottom of page 2
<hexdump0815> xdarklight: ah - ok i did not look that far - i think i'll never understand the order of the github commit history
<hexdump0815> xdarklight: the m8s problem looks like the soldering of the memory chips or the soc getting bad - the warmer the box gets the more unstable it gets - looks like with memtest=64 it does not even boot up properly anymore ... maybe i should put some ice cubes on top of it :)
<xdarklight> hexdump0815: heh - or use liquid nitrogen ;)
yann has joined #linux-amlogic
warpme_ has joined #linux-amlogic
<hexdump0815> xdarklight: the usb phy fix does not seem to work - this is the dmesg: https://pastebin.com/raw/vCUcRU1c and this is the patch i used (slightly adapted to fit the 5.6.8 kernel i use): https://github.com/hexdump0815/linux-mainline-and-mali-amlogic-kernel/blob/master/misc.m8x/mxiii-usb-phy-fix.patch
<hexdump0815> xdarklight: does it actually apply to the mxiii, which as we found out is meson8 and not meson8m2?
<xdarklight> hexdump0815: can you please pick all four patches which I committed yesterday to https://github.com/xdarklight/linux/commits/meson-mx-integration-5.8-20200501/drivers/phy/amlogic/phy-meson8b-usb2.c ? these should all apply cleanly, even to 5.6
<hexdump0815> xdarklight: ah - i see - will do ...
sputnik_ has quit [Ping timeout: 240 seconds]
<hexdump0815> xdarklight: good news - it works - my mxiii has usb now - thanks a lot!
<xdarklight> hexdump0815: nice, so I'll be sending patches later :)
<hexdump0815> xdarklight: please put me on cc, so that i can add my tested-by, as i'm not on the list myself
<hexdump0815> xdarklight: do you think it would make sense to bring in the dts files i'm using on my boxes (in cleaned up form) too? i'm now using meson8-mxii.dts* and meson8m2-m8s-dvfs.dts from https://github.com/hexdump0815/linux-mainline-and-mali-amlogic-kernel/tree/master/misc.m8x/dtb
<xdarklight> hexdump0815: I think upstreaming them makes sense, because whenever I do larger changes (like fixing RGMII Ethernet for example) I'm always searching in all existing .dts and update them accordingly
hexdump0815 has quit [Remote host closed the connection]
drieschel has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
Xogium has quit [Quit: Leaving.]
Xogium has joined #linux-amlogic
drieschel has quit [Ping timeout: 272 seconds]
drieschel has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 256 seconds]
vagrantc has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 256 seconds]
drieschel has quit [Quit: drieschel]
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 260 seconds]