From: Scott Wood <scottwood@freescale.com>
To: skepper@ukf.net
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Early boot problem with MPC8247 and Linux 2.6.26
Date: Thu, 28 Aug 2008 12:57:06 -0500 [thread overview]
Message-ID: <48B6E6F2.9020403@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0808281747440.24851@chara.vm.bytemark.co.uk>
Chris Skepper wrote:
> Thanks so much for your help so far. I was able to find out this
> address from the bootloader and get some output on the early debug
> console which was very pleasing. It now gets as far as console_init()
> called from init/main.c, which completes but then any printk seems to
> stall it and you get no more output.
>
> I am using SMC1 and have this in the DTS file for the linux,stdout-path:
>
> serial@11a80 {
> device_type = "serial";
> compatible = "fsl,mpc8247-smc-uart",
> "fsl,cpm2-smc-uart";
> reg = <0x11a80 0x20 0x87fc 2>;
> interrupts = <4 8>;
> interrupt-parent = <&PIC>;
> fsl,cpm-brg = <7>;
> fsl,cpm-command = <0x1d000000>;
> };
>
> Any ideas what sorts of things I should check next?
Check the BRG frequency (clock-frequency in the brg node), and the baud
rate that the driver is trying to set. As a quick check, you can
disable calls to cpm2_setbrg() to see if that's the problem.
-Scott
next prev parent reply other threads:[~2008-08-28 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 15:29 Early boot problem with MPC8247 and Linux 2.6.26 Chris Skepper
2008-08-22 17:06 ` Scott Wood
2008-08-26 12:00 ` Chris Skepper
2008-08-26 14:03 ` Scott Wood
2008-08-26 17:09 ` Chris Skepper
2008-08-26 17:24 ` Scott Wood
2008-08-27 13:30 ` Chris Skepper
2008-08-27 15:01 ` Scott Wood
2008-08-28 17:00 ` Chris Skepper
2008-08-28 17:57 ` Scott Wood [this message]
2008-08-27 15:01 ` Scott Wood
[not found] ` <1732780698.20080825104615@epygiarm.am>
2008-08-26 11:17 ` Chris Skepper
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=48B6E6F2.9020403@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=skepper@ukf.net \
/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).