On Sun, 16 Feb 2014, Geert Uytterhoeven wrote:
On Sat, Feb 15, 2014 at 5:47 AM, Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> wrote:--- linux-m68k.orig/arch/m68k/Kconfig.debug 2014-02-15 14:49:18.000000000 +1100 +++ linux-m68k/arch/m68k/Kconfig.debug 2014-02-15 15:06:30.000000000 +1100 @@ -12,12 +12,15 @@ config BOOTPARAM_STRING config EARLY_PRINTK bool "Early printk" - depends on MVME16x || MAC help Write kernel log output directly to a serial port. + Where implemented, output goes to the framebuffer as well. + + Pass "earlyprintk=debug" on the kernel command line to get a + boot console (not required on MVME16x).Just "earlyprintk" should be enough?
Perhaps. I ended up using the "debug" parameter because of MVME16x. At the moment it has its own early console implementation. MVME16x might need some interrupt masking added before the head.S boot console can work there. (BTW, the interrupt problem may affect other platforms too. Atari has the same SCC initialization bugs that I fixed for the Mac. I should patch that. Does anyone know the Zilog SCC PCLK rate on Atari?) Otherwise the existing MVME16x early console could be scrapped in favour of the head.S console. Or those users might want both options: the existing console in arch/m68k/mvme16x/config.c (say, "earlyprintk=cd2401") as well as the head.S console (as "earlyprintk=debug") ... or they might want no head.S boot console at all (and "earlyprintk" would imply CD2401) ... or something completely different ...
Please also consider adding m68k to Documentation/kernel-parameters.txt
Will do. Finn -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
