From: Scott Wood <scottwood@freescale.com>
To: jeff angielski <jeff@theptrgroup.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: cpm2-scc-uart on mpc8265 not working
Date: Tue, 23 Dec 2008 13:01:55 -0600 [thread overview]
Message-ID: <495135A3.9090709@freescale.com> (raw)
In-Reply-To: <1230057813.11655.27.camel@penguin>
jeff angielski wrote:
> I fixed up the DPRAM regions.
>
> I also fixed up the muram region which had not been updated for the
> mpc8265 - it still had the old mpc8272 definitions.
>
> The kernel does not hang anymore but I still don't see anything on the
> serial port. Using an o'scope I can see data on the line, it is just
> that bit period is about 560uS - way to slow.
U-boot needs to fill in the clock-frequency property in the brg node.
> data@0 {
> /*
> reg = <0x0 0x2000 0x9800 0x800>;
> */
> compatible = "fsl,cpm-muram-data";
> reg = <0x0 0x6000 0x8000 0x1000 0xb000 0x1000>;
This is not correct -- you should only list the DPRAM regions that are
usable for arbitrary data. This is <0 0x4000>, assuming none of that
has been allocated to microcode.
-Scott
prev parent reply other threads:[~2008-12-23 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 20:21 cpm2-scc-uart on mpc8265 not working jeff angielski
2008-12-22 21:01 ` Scott Wood
2008-12-23 18:43 ` jeff angielski
2008-12-23 19:01 ` Scott Wood [this message]
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=495135A3.9090709@freescale.com \
--to=scottwood@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jeff@theptrgroup.com \
/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).