From: Valentine Barshak <vbarshak@ru.mvista.com>
To: linuxppc-dev@ozlabs.org
Cc: david@gibson.dropbear.id.au
Subject: [PATCH] PowerPC: Split early debug output and early boot console for 44x
Date: Thu, 18 Oct 2007 16:55:13 +0400 [thread overview]
Message-ID: <20071018125513.GA24673@ru.mvista.com> (raw)
Currently there's no way to enable early boot console on PowerPC 44x
not specifying uart's physical address in kernel config, which is used
for very early debug messages. This patch splits very early debug output
(which needs uart physical address in kernel config) and early boot console
(which searches for uarts in the device tree using find_legacy_serial_ports).
We enable early boot console for all 44x processors, while (dangerous)
early debug is user-selectable.
Signed-off-by: Valentine Barshak <vbarshak@ru.mvista.com>
---
arch/powerpc/Kconfig.debug | 1 -
arch/powerpc/platforms/Kconfig.cputype | 1 +
2 files changed, 1 insertion(+), 1 deletion(-)
diff -pruN linux-2.6.orig/arch/powerpc/Kconfig.debug linux-2.6/arch/powerpc/Kconfig.debug
--- linux-2.6.orig/arch/powerpc/Kconfig.debug 2007-10-18 15:59:09.000000000 +0400
+++ linux-2.6/arch/powerpc/Kconfig.debug 2007-10-18 16:08:33.000000000 +0400
@@ -216,7 +216,6 @@ config PPC_EARLY_DEBUG_BEAT
config PPC_EARLY_DEBUG_44x
bool "Early serial debugging for IBM/AMCC 44x CPUs"
depends on 44x
- select PPC_UDBG_16550
help
Select this to enable early debugging for IBM 44x chips via the
inbuilt serial port.
diff -pruN linux-2.6.orig/arch/powerpc/platforms/Kconfig.cputype linux-2.6/arch/powerpc/platforms/Kconfig.cputype
--- linux-2.6.orig/arch/powerpc/platforms/Kconfig.cputype 2007-10-18 15:59:10.000000000 +0400
+++ linux-2.6/arch/powerpc/platforms/Kconfig.cputype 2007-10-18 16:08:33.000000000 +0400
@@ -48,6 +48,7 @@ config 44x
bool "AMCC 44x"
select PPC_DCR_NATIVE
select WANT_DEVICE_TREE
+ select PPC_UDBG_16550
config E200
bool "Freescale e200"
reply other threads:[~2007-10-18 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071018125513.GA24673@ru.mvista.com \
--to=vbarshak@ru.mvista.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox