_whitelogger has joined #linux-exynos
arnd has quit [Ping timeout: 276 seconds]
arnd has joined #linux-exynos
aalm has quit [Ping timeout: 246 seconds]
aalm has joined #linux-exynos
mszyprow has joined #linux-exynos
adjtm has quit [Ping timeout: 246 seconds]
adjtm has joined #linux-exynos
aalm has quit [Quit: xyz 2.3]
ahajda has quit [Ping timeout: 246 seconds]
ahajda has joined #linux-exynos
ahajda has quit [Remote host closed the connection]
ahajda has joined #linux-exynos
genii has joined #linux-exynos
mszyprow has quit [Ping timeout: 245 seconds]
gordanb has joined #linux-exynos
<gordanb> I have this rather odd issue on the Exynos based Samsung Chromebook 2. A kernel built with CONFIG_ARM_BIG_LITTLE_CPUIDLE fails to boot (only tried 4.9.x series kernels).
<gordanb> If I disable the option, it works.
<gordanb> Anyone else hit this? Is there a patch/fix/workaround, other than to disable the option?
adjtm has quit [Ping timeout: 258 seconds]
adjtm has joined #linux-exynos
dllud_ has joined #linux-exynos
dllud has quit [Ping timeout: 245 seconds]
dllud_ is now known as dllud
<freekurt> hexdump0815: thanks for providing that info for the snow chromebook and odroid u3! do you happen to have a support matrix for either of them to show what is working and what isn't working when using the mainline kernel?
aalm has joined #linux-exynos
mszyprow|home has joined #linux-exynos
putti_ has joined #linux-exynos
Putti has quit [Read error: Connection reset by peer]
mszyprow|home has quit [Ping timeout: 276 seconds]
aalm has quit [Ping timeout: 244 seconds]
putti_ is now known as Putti
aalm has joined #linux-exynos
gordanb has quit [Quit: Konversation terminated!]