From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Christoph Egger <siccegge@cs.fau.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
vamos@i4.informatik.uni-erlangen.de
Subject: Re: [PATCH 4/5] Removing dead CONFIG_SERIAL_TEXT_DEBUG
Date: Wed, 9 Jun 2010 06:28:15 -0400 [thread overview]
Message-ID: <20100609102815.GG7801@zod.rchland.ibm.com> (raw)
In-Reply-To: <ddcbd960ff300073939bb0c6f20a38118c0875d4.1275925219.git.siccegge@cs.fau.de>
On Wed, Jun 09, 2010 at 12:00:46PM +0200, Christoph Egger wrote:
>CONFIG_SERIAL_TEXT_DEBUG doesn't exist in Kconfig, therefore removing all
>references for it from the source code.
>
>Signed-off-by: Christoph Egger <siccegge@cs.fau.de>
It would be better to conver this to work with CONFIG_PPC_EARLY_DEBUG and
CONFIG_PPC_EARLY_DEBUG_40x. I'd rather just leave this for now until we can
get it switched over.
josh
>---
> arch/powerpc/kernel/head_40x.S | 19 -------------------
> 1 files changed, 0 insertions(+), 19 deletions(-)
>
>diff --git a/arch/powerpc/kernel/head_40x.S b/arch/powerpc/kernel/head_40x.S
>index a90625f..1a10e4d 100644
>--- a/arch/powerpc/kernel/head_40x.S
>+++ b/arch/powerpc/kernel/head_40x.S
>@@ -939,25 +939,6 @@ initial_mmu:
> tlbwe r4,r0,TLB_DATA /* Load the data portion of the entry */
> tlbwe r3,r0,TLB_TAG /* Load the tag portion of the entry */
>
>-#if defined(CONFIG_SERIAL_TEXT_DEBUG) && defined(SERIAL_DEBUG_IO_BASE)
>-
>- /* Load a TLB entry for the UART, so that ppc4xx_progress() can use
>- * the UARTs nice and early. We use a 4k real==virtual mapping. */
>-
>- lis r3,SERIAL_DEBUG_IO_BASE@h
>- ori r3,r3,SERIAL_DEBUG_IO_BASE@l
>- mr r4,r3
>- clrrwi r4,r4,12
>- ori r4,r4,(TLB_WR|TLB_I|TLB_M|TLB_G)
>-
>- clrrwi r3,r3,12
>- ori r3,r3,(TLB_VALID | TLB_PAGESZ(PAGESZ_4K))
>-
>- li r0,0 /* TLB slot 0 */
>- tlbwe r4,r0,TLB_DATA
>- tlbwe r3,r0,TLB_TAG
>-#endif /* CONFIG_SERIAL_DEBUG_TEXT && SERIAL_DEBUG_IO_BASE */
>-
> isync
>
> /* Establish the exception vector base
>--
>1.6.3.3
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@lists.ozlabs.org
>https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2010-06-09 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 9:58 [PATCH 0/5] Removing dead code Christoph Egger
2010-06-09 9:59 ` [PATCH 1/5] Removing dead BOOK3E_MMU_TLB_STATS Christoph Egger
2010-06-10 5:20 ` Benjamin Herrenschmidt
2010-06-09 9:59 ` [PATCH 2/5] Removing dead CONFIG_HIGHPTE Christoph Egger
2010-06-09 10:00 ` [PATCH 3/5] Removing dead CONFIG_SMP_750 Christoph Egger
2010-06-09 12:35 ` Josh Boyer
2010-06-10 6:14 ` Benjamin Herrenschmidt
2010-06-10 12:23 ` Christoph Egger
2010-06-11 6:41 ` Benjamin Herrenschmidt
2010-06-09 10:00 ` [PATCH 4/5] Removing dead CONFIG_SERIAL_TEXT_DEBUG Christoph Egger
2010-06-09 10:28 ` Josh Boyer [this message]
2010-06-09 10:01 ` [PATCH 5/5] Removing dead CONFIG_PPC47x Christoph Egger
2010-06-09 11:02 ` [PATCH 5b/5] " Christoph Egger
2010-06-09 12:05 ` Josh Boyer
2010-06-10 8:59 ` Benjamin Herrenschmidt
2010-06-10 18:46 ` [PATCH 0/5] Removing dead code Joe Perches
2010-06-11 7:26 ` Reinhard Tartler
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=20100609102815.GG7801@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=siccegge@cs.fau.de \
--cc=vamos@i4.informatik.uni-erlangen.de \
/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
all inboxes | Powered by JetHome®