krzk changed the topic of #linux-exynos to: Samsung S3C24xx and S3C64xx planned deprecation and removal (see LKML) | Linux Samsung SoC Exynos | https://exynos.wiki.kernel.org | This channel is logged: https://libera.irclog.whitequark.org/linux-exynos
jma has quit [Remote host closed the connection]
hexdump0815 has quit [Ping timeout: 256 seconds]
hexdump0815 has joined #linux-exynos
jma has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-exynos
GNUtoo has quit [Ping timeout: 240 seconds]
GNUtoo_ has joined #linux-exynos
GNUtoo_ has quit [Remote host closed the connection]
GNUtoo has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
<jma> Just to clarify things the Nexus 10 uses a 3.4 kernel and I'm trying to run 5.9.18.5. I found data log in /proc/last_kmsg but this log was created when I tried to boot my boot image with a 3.4 kernel to check that everything was good
<jma> I guess I can enable PSTORE on 5.9.18 and capture the log from Recovery. But 3.4 doesn't support PSTORE.So I'm looking for a way to read the PSTORE data using an old kernel.
<jma> I mean 3.4 is supporting ram-oops but not sure about the compatibility level
GNUtoo has quit [Ping timeout: 240 seconds]
GNUtoo has joined #linux-exynos
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-exynos
<jma> I think the problem is that AUTO_ZRELADDR is enabled and the zimage is actually loader at 0x10008000 offset (> 128MB). Threfore kernel is deflated at 0x10000000 which is too close to the zImage. atags are overwritten as well
jma has quit [Remote host closed the connection]