On 2019-01-22 08:23 +0000, Ian Campbell wrote: > On Tue, 2019-01-22 at 04:31 +0000, Wookey wrote: > > On 2019-01-20 03:02 +0000, Ben Hutchings wrote: > > > Reading /proc/consoles is exactly what you should do. > > > > Checking this on a booted thunderx machine (with no explicit kernel cmdline > > options) it lists > > ttyAMA0 > > > > If I boot with explicit console=tty0 console=ttyAMA0 on the kernel cmdline > > then they both appear in /proc/consoles, AMA0 last > > > > If I boot with explicit console=tty0 on the kernel cmdline > > then they both appear in /proc/consoles, AMA0 still last > > Do the various flags not differ between the different cases?
You are right. I wasn't taking note of those: E=enabled C=preferred console p=used for printk buffer a=safe to use when CPU is offline console=tty0 tty0 -WU (EC p ) 4:7 ttyAMA0 -W- (E p a) 204:64 console=ttyAMA0 tty0 -WU (E p ) 4:7 ttyAMA0 -W- (EC p a) 204:64 console=tty0 console=ttyAMA0 tty0 -WU (E p ) 4:7 ttyAMA0 -W- (E p a) 204:64 Any idea how we should choose a D-I primary console when none of them is marked 'preferred'? Or should D-i do away with the concept and try to treat them all equally (which is a slightly more intrusive change). Currently I use the one marked 'C' or the last one if none. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
