Hi folks,


I'm currently trying to get 4.11 running on an sitara-based machine
(*1). The board is quite similar to the am335xevm, so I've taken it as
reference and patched up the dts w/ things differing between the board
init routines from the old 3.2 kernel (the vendor is still on some old
3.2 ti kernel w/ some patches)

early_print() and DTS loading works, but printk() doesn't print
anything. I've added lots of early_print() calls and confirmed
that at least the idle and init tasks come up and lots of device
probing on the platform bus is happening (according to fdt_* calls)

At that point I should see lots of printk() outputs, but get nothing.

I've confirmed that the console_initcall's have been called, so the
console subsystem *should* be initialized. But I dont see any calls
to serial_omap_console_write(), even though serial_omap_init() ran
through properly.

Is there anything in the path from printk() to the console driver's
write() function that could be blocking the output ? Maybe held back
in buffer which for some reason isn't written out yet ?

CONFIG_DEBUG_LL=y
CONFIG_DEBUG_AM33XXUART1=y
CONFIG_DEBUG_OMAP2PLUS_UART=y
CONFIG_DEBUG_LL_INCLUDE="debug/omap2plus.S"

CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_FSL=y
CONFIG_SERIAL_8250_OMAP=y
CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y
CONFIG_SERIAL_OF_PLATFORM=y

CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_OMAP=y
CONFIG_SERIAL_OMAP_CONSOLE=y

CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_DUMMY_CONSOLE=y

CONFIG_CMDLINE="root=/dev/mmcblk0p2 rootwait console=ttyO0,115200"


thx
--mtx


*1)
https://www.duagon.com/cn/products/productdetails/productfamily/ionia/show/

--
Enrico, Sohn von Wilfried, a.d.F. Weigelt,
metux IT consulting
+49-151-27565287