<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 ;)
<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]