From: Eugene Surovegin <ebs@ebshome.net>
To: Josh Boyer <jdub@us.ibm.com>
Cc: paulus@samba.org, mporter@embeddedalley.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [v3] PPC 4xx: Enable XMON on PPC 4xx boards
Date: Thu, 7 Sep 2006 10:19:16 -0700 [thread overview]
Message-ID: <20060907171916.GB18929@gate.ebshome.net> (raw)
In-Reply-To: <1157639720.6098.49.camel@zod.rchland.ibm.com>
On Thu, Sep 07, 2006 at 09:35:20AM -0500, Josh Boyer wrote:
[snip]
> --- linux-2.6.orig/arch/ppc/xmon/start.c
> +++ linux-2.6/arch/ppc/xmon/start.c
> @@ -73,6 +73,27 @@ xmon_map_scc(void)
> TXRDY = 0x20;
> RXRDY = 1;
> DLAB = 0x80;
> +#elif defined(CONFIG_440EP)
> + sccd = (volatile unsigned char *) ioremap(0xef600300, 8);
> + sccc = sccd + 5;
> + TXRDY = 0x20;
> + RXRDY = 1;
> + DLAB = 0x80;
> +#elif defined(CONFIG_440SP)
> + sccd = (volatile unsigned char *) ioremap64(0x00000001f0000200ULL, 8);
> + sccc = sccd + 5;
> + TXRDY = 0x20;
> + RXRDY = 1;
> + DLAB = 0x80;
> +#elif defined(CONFIG_44x)
> + /* This is the default for 44x platforms. Any boards that have a
> + different UART address need to be put in cases before this or the
> + port will be mapped incorrectly */
> + sccd = (volatile unsigned char *) ioremap64(0x0000000140000200ULL, 8);
> + sccc = sccd + 5;
> + TXRDY = 0x20;
> + RXRDY = 1;
> + DLAB = 0x80;
There is only one line which is different, why did you put all other
under #ifdef?
Also, all these hardcoded addresses are already available as defines,
why just not use them?
--
Eugene
next prev parent reply other threads:[~2006-09-07 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 14:35 [PATCH] [v3] PPC 4xx: Enable XMON on PPC 4xx boards Josh Boyer
2006-09-07 17:19 ` Eugene Surovegin [this message]
2006-09-07 18:08 ` Josh Boyer
2006-09-08 1:03 ` Benjamin Herrenschmidt
2006-09-08 1:10 ` Josh Boyer
2006-09-07 17:20 ` Matt Porter
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=20060907171916.GB18929@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=jdub@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mporter@embeddedalley.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).