From: jeff angielski <jeff@theptrgroup.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Jean-Michel Hautbois <jhautbois@gmail.com>
Subject: Re: [MPC8272ADS]Cannot start my Linux Kernel
Date: Wed, 21 Jan 2009 10:42:10 -0500 [thread overview]
Message-ID: <1232552530.7186.5.camel@penguin> (raw)
In-Reply-To: <20090120163155.GA8978@ld0162-tx32.am.freescale.net>
On Tue, 2009-01-20 at 10:31 -0600, Scott Wood wrote:
> On Tue, Jan 20, 2009 at 11:56:58AM +0100, Jean-Michel Hautbois wrote:
> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
> > Kernel command line: root=/dev/ram rw
> > PID hash table entries: 256 (order: 8, 1024 bytes)
> > time_init: decrementer frequency = 25.000000 MHz
> > time_init: processor frequency = 400.000000 MHz
> > clocksource: timebase mult[a000000] shift[22] registered
> > clockevent: decrementer mult[666] sh�
>
> That looks like something is failing when the real (as opposed to early
> debug) serial driver starts. Try commenting out the call to cpm_setbrg
> in drivers/serial/cpm_uart/cpm_uart_cpm2.h; if that makes a difference,
> there's something wrong with the brg node in the device tree.
I used the mpc8272ads as the basis for my mpc8265 port to 2.6 and found
that to get the serial ports to clock correctly, I needed to add
"clock-frequency" to the brg node in the DTS file.
Here is mine:
brg@119f0 {
compatible = "mpc8265-brg",
"fsl,cpm2-brg",
"fsl,cpm-brg";
reg = <0x119f0 0x10 0x115f0 0x10>;
clock-frequency = <0>;
};
Of course, you also need to update your ft_blob_update() in u-boot to
fill in the correct value.
The default values in the cpm2 code did not work for my system clock
configuration.
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next prev parent reply other threads:[~2009-01-21 15:42 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 [this message]
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
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=1232552530.7186.5.camel@penguin \
--to=jeff@theptrgroup.com \
--cc=jhautbois@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).