linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@embeddedalley.com>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] [v2] PPC 4xx: Enable XMON on PPC 4xx boards
Date: Thu, 7 Sep 2006 09:23:19 -0400	[thread overview]
Message-ID: <20060907132319.GA476@matthew-porters-computer.local> (raw)
In-Reply-To: <1157632424.6098.32.camel@zod.rchland.ibm.com>

On Thu, Sep 07, 2006 at 07:33:44AM -0500, Josh Boyer wrote:
> --- linux-2.6.orig/arch/ppc/xmon/start.c
> +++ linux-2.6/arch/ppc/xmon/start.c
> @@ -73,6 +73,12 @@ xmon_map_scc(void)
>  	TXRDY = 0x20;
>  	RXRDY = 1;
>  	DLAB = 0x80;
> +#elif ( defined(CONFIG_440) || defined(CONFIG_440GX) )
> +	sccd = (volatile unsigned char *) ioremap64(0x0000000140000200ULL, 8);
> +	sccc = sccd + 5;
> +	TXRDY = 0x20;
> +	RXRDY = 1;
> +	DLAB = 0x80;
>  #endif /* platform */

These can be represented with CONFIG_44x. Though it doesn't work for
440EP since it doesn't have the 36-bit memory map. It should be:

+#elif ( defined(CONFIG_44x) && !defined(CONFIG_440EP) )
+     sccd = (volatile unsigned char *) ioremap64(0x0000000140000200ULL, 8);
+     sccc = sccd + 5;
+     TXRDY = 0x20;
+     RXRDY = 1;
+     DLAB = 0x80;

Adding in another case would enable 440EP as well:

+#elif ( defined(CONFIG_440EP) )
+     sccd = (volatile unsigned char *) ioremap(0xef600300, 8);
+     sccc = sccd + 5;
+     TXRDY = 0x20;
+     RXRDY = 1;
+     DLAB = 0x80;

-Matt

  reply	other threads:[~2006-09-07 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 12:33 [PATCH] [v2] PPC 4xx: Enable XMON on PPC 4xx boards Josh Boyer
2006-09-07 13:23 ` Matt Porter [this message]
2006-09-07 13:29   ` Josh Boyer

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=20060907132319.GA476@matthew-porters-computer.local \
    --to=mporter@embeddedalley.com \
    --cc=jdub@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --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).