From: David Gibson <david@gibson.dropbear.id.au>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/6] PowerPC 440EPx: Sequoia bootwrapper
Date: Wed, 1 Aug 2007 12:12:49 +1000 [thread overview]
Message-ID: <20070801021249.GD31391@localhost.localdomain> (raw)
In-Reply-To: <200707311342.46555.sr@denx.de>
On Tue, Jul 31, 2007 at 01:42:46PM +0200, Stefan Roese wrote:
> On Tuesday 31 July 2007, Valentine Barshak wrote:
> > > Is treeboot-* really needed on Sequoia? From my understanding this is
> > > only needed for platforms using OpenBIOS as bootloader.
> >
> > Right, it's not used for u-boot. I've included it just in case.
>
> I think we should drop it, when it's not used at all.
>
> You didn't comment on my review down below in the code. Perhaps you didn't see
> it. Here again the original review with 2 small comments.
>
> Thanks for the good work.
>
> > +++ linux/arch/powerpc/boot/sequoia.c 2007-07-27
> 20:59:09.000000000 +0400
[snip]
> > +static void ibm440epx_fixup_memsize(void)
> > +{
> > + unsigned long val, max_cs, max_col, max_row;
> > + unsigned long cs, col, row, bank, dpath;
> > + unsigned long memsize;
> > +
> > + mtdcr(DCRN_SDRAM0_CFGADDR, 2);
> > + val = mfdcr(DCRN_SDRAM0_CFGDATA);
>
> Again, mfsdram() functions would be handy here.
I concur, also add a #define for the value written to CFGADDR.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-08-01 2:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 15:14 [PATCH 4/6] PowerPC 440EPx: Sequoia bootwrapper Valentine Barshak
2007-07-31 5:54 ` Stefan Roese
2007-07-31 11:19 ` Valentine Barshak
2007-07-31 11:42 ` Stefan Roese
2007-07-31 12:42 ` Valentine Barshak
2007-08-01 2:12 ` David Gibson [this message]
2007-08-02 20:29 ` Josh Boyer
2007-08-03 6:38 ` Stefan Roese
2007-08-03 12:59 ` 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=20070801021249.GD31391@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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).