From: Daniel Ng99 <daniel_ng11@lycos.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: [MPC8272ADS]Cannot start my Linux Kernel
Date: Thu, 22 Jan 2009 16:21:46 -0800 (PST) [thread overview]
Message-ID: <21616515.post@talk.nabble.com> (raw)
In-Reply-To: <20090122173622.GA18427@ld0162-tx32.am.freescale.net>
Scott Wood-2 wrote:
>
> On Wed, Jan 21, 2009 at 06:15:26PM -0800, Daniel Ng99 wrote:
>> Adding 'clock-frequency = <0>;' to the brg node doesn't seem to make a
>> difference to my board's behaviour.
>
> Try setting it to the actual BRG clock.
>
My console runs at a baud rate of 115,200, so that means a BRGCLK of 35 for
a 66-MHz input clock (according to the PQ2 Reference Manual).
Then I realised u-boot reports the brg clock to be 33Mhz at boot-up:
MPC8247 Clock Configuration
- Bus-to-Core Mult 5x, VCO Div 2, 60x Bus Freq 20-60 , Core Freq 100-300
- dfbrg 1, corecnf 0x1b, busdf 7, cpmdf 1, plldf 0, pllmf 7, pcidf 7
- vco_out 528000000, scc_clk 132000000, brg_clk 33000000
- cpu_clk 330000000, cpm_clk 264000000, bus_clk 66000000
So maybe 35 x 2 = 70 is the correct value?
Anyway, I tried all these but still they made no difference:
clock-frequency = <35>
clock-frequency = <0x23>
clock-frequency = <115200>
clock-frequency = <1c200>
clock-frequency = <70>
clock-frequency = <17>
clock-frequency = <66>
clock-frequency = <33>
Can you suggest any other values?
What is the effect of just not calling set_brg()? I still get console
output, so am I setting myself up for some sort of problem in the future?
What is the effect of setting "fsl,cpm-brg = <0>" in the 'serial' device
tree node?
--
View this message in context: http://www.nabble.com/-MPC8272ADS-Cannot-start-my-Linux-Kernel-tp21476017p21616515.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-01-23 0:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 11:42 [MPC8272ADS]Cannot start my Linux Kernel Jean-Michel Hautbois
2009-01-15 12:52 ` Anatolij Gustschin
2009-01-15 13:10 ` Jean-Michel Hautbois
2009-01-15 14:25 ` Anatolij Gustschin
2009-01-15 15:06 ` Jean-Michel Hautbois
2009-01-16 12:06 ` Jean-Michel Hautbois
2009-01-16 17:29 ` Scott Wood
2009-01-16 17:40 ` Jean-Michel Hautbois
2009-01-16 17:44 ` Jean-Michel Hautbois
2009-01-16 17:53 ` Jean-Michel Hautbois
2009-01-16 18:02 ` Scott Wood
2009-01-16 18:23 ` Jean-Michel Hautbois
2009-01-20 10:56 ` Jean-Michel Hautbois
2009-01-20 16:27 ` Jean-Michel Hautbois
2009-01-20 17:51 ` Scott Wood
2009-01-20 16:31 ` Scott Wood
2009-01-20 17:05 ` Jean-Michel Hautbois
2009-01-20 17:16 ` Scott Wood
2009-01-20 17:32 ` Jean-Michel Hautbois
2009-01-20 17:35 ` Scott Wood
2009-01-21 15:42 ` jeff angielski
2009-01-21 16:15 ` Jean-Michel Hautbois
2009-01-22 2:15 ` Daniel Ng99
2009-01-22 17:36 ` Scott Wood
2009-01-23 0:21 ` Daniel Ng99 [this message]
2009-01-23 0:46 ` Daniel Ng99
2009-01-23 16:17 ` Scott Wood
2009-01-22 2:17 ` Daniel Ng99
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=21616515.post@talk.nabble.com \
--to=daniel_ng11@lycos.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.