<chewitt>
^ put that on an SD card and boot a LePotato
<chewitt>
NB: the image contains my wrong audio routing stuff not your latest patches, but the glitch is lower level anyway
yann|work has joined #linux-amlogic
psydruid has quit [Quit: killed]
la-s has quit [Quit: killed]
psydruid has joined #linux-amlogic
warpme_ has joined #linux-amlogic
yann|work is now known as yann
la-s has joined #linux-amlogic
ldevulder_ has quit [Quit: Leaving]
ldevulder has joined #linux-amlogic
random_yanek has quit [Ping timeout: 260 seconds]
random_yanek has joined #linux-amlogic
Barada has quit [Quit: Barada]
sputnik_ has quit [Ping timeout: 260 seconds]
damex has quit [Remote host closed the connection]
damex has joined #linux-amlogic
jelly-home has quit [Read error: Connection reset by peer]
jelly-home has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
jelly-home is now known as jelly
niceplaces has quit [Ping timeout: 240 seconds]
niceplace has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 260 seconds]
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
plntyk has quit [Read error: Connection reset by peer]
plntyk has joined #linux-amlogic
hexdump0815 has joined #linux-amlogic
<hexdump0815>
xdarklight: i gave 5.6/5.7 a try on a mxIII box and it was ok on 5.6.8 (no usb and no eth) and a bit worse on your latest integration tree
<hexdump0815>
xdarklight: did you have mx3 somehow working already? it looks to me like usb is not powered up properly (android dtb has "gpio-vbus-power = "GPIOZ_1";" - does this give an idea maybe?
<hexdump0815>
xdarklight: ethernet seems to be probed correctly and does not give any error, but simply does not work and does not generate any interrupt ... any idea how to get usb and eth working?
<plntyk>
you already checked for ethernet and usb functions in the bootloader ?
<hexdump0815>
both works well in android, so i assume it is ok - anything else i should try in u-boot?
<plntyk>
there might be something interesting in the uboot-environment or there are some uboot commands that output hardware register/directly speak to hardware so finding out pin numbers/register contents might be easier
sputnik_ has joined #linux-amlogic
<hexdump0815>
anything in /sys/kernel/debug in android which might be helpful? i looked around there but did not find anything pointing towards eth or usb
paulk-leonov has quit [Ping timeout: 244 seconds]
<hexdump0815>
nothing obvious to find in u-boot - ethmode 0,1,2 - only 0 works and is rmii external clk
paulk-leonov has joined #linux-amlogic
<xdarklight>
hexdump0815: I'll go through your messages tomorrow, today was a long day for me
<hexdump0815>
xdarklight: sure, there is no hurry - have a relaxed evening then
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
paulk-leonov has joined #linux-amlogic
paulk-leonov has quit [Excess Flood]
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
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: 260 seconds]
paulk-leonov has joined #linux-amlogic
wens has quit [*.net *.split]
probono has quit [*.net *.split]
wens has joined #linux-amlogic
probono has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
<hexdump0815>
xdarklight: more meson8 testing with 5.6.8 - mxq runs very nice - m8s runs quite good, but there seems to be some instability due to the memory timing
<hexdump0815>
xdarklight: for instance "7z b" reliably gives a decoding error soon and a make -j4 kernel compile soon gives internal compiler errors
<hexdump0815>
xdarklight: i think this is independent of cpu clock (its the same at the default 1.2ghz or if i unlock the opp by fake voltages up to 1.8ghz or lower max cpu freq to 1ghz
<hexdump0815>
xdarklight: is the memory timing for meson8m2 defined in the bootloader or in the kernel later? ... i did not yet do any heavy usb testing
<hexdump0815>
xdarklight: one more note regarding m8s - with normal load it runs quite stable - i was able to run a full xfce session via xpra for quite a while without any errors
etrig has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 260 seconds]
hexdump0815 has quit [Remote host closed the connection]