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: 248 seconds]
hexdump0815 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
mszyprow has joined #linux-exynos
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-exynos
jma 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]
mszyprow^home has joined #linux-exynos
mszyprow has quit [Ping timeout: 276 seconds]
jma has joined #linux-exynos
krzk has quit [Quit: leaving]
<jma> Hi, I'm trying to build a maineline kernel for Nexus 10 exynos-5250
krzk has joined #linux-exynos
<jma> Problem is I trued to beet it using fastboot boot and nothing happens. No error from bootloader but screen stays blank
<krzk> jma: try using "earlycon" in opts
<krzk> jma: anyway, debugging/bringup exynos without serial console is a pain... I don't know how all community-folks are able to do it :)
<jma> I'm pretty sure that my display config is ok in dts
<jma> I put console=tty0 kernel args in dts, so you suggest to add earlycon here ?
<krzk> jma: actually that would make sense only if you had console/serial output, but I guess you don't have?
<jma> no
tobiasjakobi has joined #linux-exynos
tobiasjakobi has quit [Remote host closed the connection]
mszyprow^home has quit [Ping timeout: 260 seconds]
<jma> no change. display stays blank, no backlight
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
leming has quit [*.net *.split]
leming has joined #linux-exynos