On Tue, 24 Dec 2013, Thorsten Glaser wrote: > Finn Thain dixit: > > > > > > > Why is CONFIG_SERIAL_PMACZILOG to be disabled? > > Because of crashes in multiplatform kernels when it is enabled.
That crash requires both CONFIG_SERIAL_PMACZILOG && !CONFIG_EARLY_CONSOLE. See http://lists.debian.org/debian-68k/2013/11/msg00167.html CONFIG_EARLY_CONSOLE got disabled by default because I changed the default. I had mistakenly assumed that the new mainline default would get over-ridden in Debian kernel configs. CONFIG_EARLY_CONSOLE=n makes it difficult to help Debian users (for example the boot failure due to lack of FPU emulation was diagnosed using the early console and the issue with '030 futuex support was mis-diagnosed due to lack of the early console). > The disabling CONFIG_SERIAL_PMACZILOG is also for 3.12 only (dunno about > 3.13, but I think Geert has already? will? fix it for the next one). > There were several problems with debugging and multi? platform kernels. I suggest that these should be explicitly enabled in the Debian config: CONFIG_EARLY_CONSOLE=y CONFIG_SERIAL_PMACZILOG=y CONFIG_SERIAL_PMACZILOG_TTYS=y CONFIG_SERIAL_PMACZILOG_CONSOLE=y I think this is better than assuming that mainline does what your users want. Reason being that the change I made to the mainline default has impacted only Debian users adversely (I've not counted Geert, who fixed the crash for mainline users, in case any of them configured CONFIG_EARLY_CONSOLE=n). Finn -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.LNX.2.00.1312281358180.17160@nippy.intranet
