summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorMichael Ellerman <michael@ellerman.id.au>2008-04-24 07:13:13 +0200
committerPaul Mackerras <paulus@samba.org>2008-04-24 13:08:11 +0200
commitc7afb4e22961b5ec88eb6f7b81260dafa9f287c7 (patch)
tree8a7d966e1547598331019155de0c3f9aadcc0a29 /arch
parent[POWERPC] Raise the upper limit of NR_CPUS and move the pacas into the BSS (diff)
downloadlinux-c7afb4e22961b5ec88eb6f7b81260dafa9f287c7.tar.xz
linux-c7afb4e22961b5ec88eb6f7b81260dafa9f287c7.zip
[POWERPC] Set udbg_console index to 0
Because the udbg_console has CON_ENABLED set, it's possible that when we register it with the console code the index won't be set. This leads to slightly confusing boot messages like: [ 0.000000] console [udbg-1] enabled We could remove CON_ENABLED, but we don't want to do that, we always want the udbg console to be activated, even if the user specified some other console on the command line. The simplest fix seems to be just to set the index to 0 by hand. There is no issue with duplicate udbg consoles, as we guard against registering multiple times in register_early_udbg_console(). Signed-off-by: Michael Ellerman <michael@ellerman.id.au> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/powerpc/kernel/udbg.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/powerpc/kernel/udbg.c b/arch/powerpc/kernel/udbg.c
index 7aad6203e411..9ac5f3aad5e8 100644
--- a/arch/powerpc/kernel/udbg.c
+++ b/arch/powerpc/kernel/udbg.c
@@ -155,7 +155,7 @@ static struct console udbg_console = {
.name = "udbg",
.write = udbg_console_write,
.flags = CON_PRINTBUFFER | CON_ENABLED | CON_BOOT,
- .index = -1,
+ .index = 0,
};
static int early_console_initialized;