summaryrefslogtreecommitdiffstats
path: root/tools/arch/s390/include
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2018-12-15 00:57:11 +1100
committerMichael Ellerman <mpe@ellerman.id.au>2018-12-20 22:21:20 +1100
commit2b874a5c7b75fdc90fdd1e2ffaa3ec5a9d21e253 (patch)
tree137c7aa16d292affea432eabf5b121b0b8fc6e94 /tools/arch/s390/include
parent2fea82db113e4422ef5c8e6209908806e5fb6b63 (diff)
downloadlinux-2b874a5c7b75fdc90fdd1e2ffaa3ec5a9d21e253.tar.bz2
powerpc/configs: Don't enable PPC_EARLY_DEBUG in defconfigs
This reverts the remains of commit b9ef7d6b11c1 ("powerpc: Update default configurations"). That commit was proceeded by a commit which added a config option to control use of BOOTX for early debug, ie. PPC_EARLY_DEBUG_BOOTX, and then the update of the defconfigs was intended to not change behaviour by then enabling the new config option. However enabling PPC_EARLY_DEBUG had other consequences, notably causing us to register the udbg console at the end of udbg_early_init(). This means on a system which doesn't have anything that BOOTX can use (most systems), we register the udbg console very early but the bootx code just throws everything away, meaning early boot messages are never printed to the console. What we want to happen is for the udbg console to only be registered later (from setup_arch()) once we've setup udbg_putc, and then all early boot messages will be replayed. Fixes: b9ef7d6b11c1 ("powerpc: Update default configurations") Reported-by: Torsten Duwe <duwe@lst.de> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'tools/arch/s390/include')
0 files changed, 0 insertions, 0 deletions