<hexdump>
LiquidAcid: yes right, for instance all the boot messages on the framebuffer are gone as soon as a serial console is configured as well - even if the fb console on the command line is the second cmdline arg and thus should be primary
Ultrasauce has quit [Remote host closed the connection]
mszyprow_ has joined #linux-exynos
mszyprow has quit [Ping timeout: 240 seconds]
mixfix41 has joined #linux-exynos
<mixfix41>
huh so i wasnt able to even compile the chromeos with some recommended options for nfs autofs + whatever config bt i saw also
<mixfix41>
but i dont know maybe bluetooth isnt very viable... hmm i even read a few posts thats one person had mostly everything going but on archarm and a mainline kernel but he stopped posting...
<mixfix41>
oh well still a cool side project
<mixfix41>
well i can stilltr ansfer my files since i got to learning the bluetoothctl plus starting the pulse audio to get those device paired and connected so but definitely a little shadier route as i could just use a cord for my needs
ansiwon has quit [Quit: leaving]
ansiwon has joined #linux-exynos
afaerber has quit [Ping timeout: 246 seconds]
afaerber has joined #linux-exynos
nighty- has quit [Quit: Disappears in a puff of smoke]
wiewo has quit [Quit: I'm out]
wiewo has joined #linux-exynos
ansiwon has quit [Remote host closed the connection]
ansiwon has joined #linux-exynos
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-exynos
genii has joined #linux-exynos
nighty- has joined #linux-exynos
mszyprow_ has quit [Ping timeout: 248 seconds]
LiquidAcid has joined #linux-exynos
<LiquidAcid>
hexdump, actually i'm not sure how the kernel's printk is supposed to behave in such a case
<LiquidAcid>
also, i don't think that fbcon is really suitable for this anyway, considering how late drm is loaded in the process
<hexdump>
not a really big problem anyway
<zombah>
it is possible define multiple console outputs in cmdline like this: console=ttySAC3,115200n8 console=tty
<LiquidAcid>
zombah, that's not accurate
<LiquidAcid>
the docs only say that you can specify one console per type, the problem here most likely is that the kernel considers tty0 and ttyS0 separate types, but not ttySAC0 and tty0
<LiquidAcid>
see in particular kernel/printk/*
<zombah>
LiquidAcid: hm it was working fine last time i tried, probably something changed lately on ttySAC type front
<LiquidAcid>
"Note that you can only define one console per device type (serial, video)." <- the question here is what type the kernel assigns to ttySAC