linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Daniel Ng99 <daniel_ng11@lycos.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [MPC8272ADS]Cannot start my Linux Kernel
Date: Fri, 23 Jan 2009 10:17:59 -0600	[thread overview]
Message-ID: <4979EDB7.7030106@freescale.com> (raw)
In-Reply-To: <21616515.post@talk.nabble.com>

Daniel Ng99 wrote:
> 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? 

Don't set it to the BRG divider, set it to the BRG *input* clock, which 
appears to be 33000000.

> 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?

You will not be able to change the baud rate from Linux.

> What is the effect of setting "fsl,cpm-brg = <0>" in the 'serial' device
> tree node?

You'll have an invalid device tree, which will cause the kernel to write 
to a reserved register.

-Scott

  parent reply	other threads:[~2009-01-23 16:18 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
2009-01-23  0:46                             ` Daniel Ng99
2009-01-23 16:17                             ` Scott Wood [this message]
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=4979EDB7.7030106@freescale.com \
    --to=scottwood@freescale.com \
    --cc=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 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).