From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: "tiejun.chen" <tiejun.chen@windriver.com>
Subject: Re: [PATCH 2/2] powerpc/405ex: support cuImage via included dtb
Date: Fri, 21 Aug 2009 08:35:58 +0200 [thread overview]
Message-ID: <200908210835.58288.sr@denx.de> (raw)
In-Reply-To: <4A8E3396.9030006@windriver.com>
On Friday 21 August 2009 07:41:42 tiejun.chen wrote:
> >> +static void kilauea_fixups(void)
> >> +{
> >> + /*TODO: Please change this as the real. Note that should be
> >> 33MHZ~100MHZ.*/
> >
> > What does that mean?
>
> It's difficult to check the sysclk value on all revision Kilauea board for
> me, and we have to check this value only by the real target, not by reading
> one register. So I hope it's safe to remind other guys here.
Kilauea uses this value (33.333MHz) on all board revisions, AFAIK. Your
comment is a bit confusing. I suggest that you just remove it.
Cheers,
Stefan
next prev parent reply other threads:[~2009-08-21 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 2:28 powerpc/405ex: Support cuImage for PPC405EX Tiejun Chen
2009-08-18 2:28 ` [PATCH 1/2] powerpc/405ex: provide necessary fixup function to support cuImage Tiejun Chen
2009-08-20 13:26 ` Josh Boyer
2009-08-21 6:00 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 2:28 ` [PATCH 2/2] powerpc/405ex: support cuImage via included dtb Tiejun Chen
2009-08-20 13:31 ` Josh Boyer
2009-08-21 5:41 ` tiejun.chen
2009-08-21 6:35 ` Stefan Roese [this message]
2009-08-21 6:39 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 3:30 ` Mailing lists (Was: Re: powerpc/405ex: Support cuImage for PPC405EX) Stephen Rothwell
2009-08-18 4:38 ` tiejun.chen
2009-08-18 3:39 ` powerpc/405ex: Support cuImage for PPC405EX Benjamin Herrenschmidt
2009-08-18 13:28 ` Josh Boyer
2009-08-19 1:45 ` tiejun.chen
2009-08-19 11:45 ` Josh Boyer
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=200908210835.58288.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tiejun.chen@windriver.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).