public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] MX5:MX53: support for freescale MX53LOCO board
Date: Thu, 14 Apr 2011 07:31:02 +0200	[thread overview]
Message-ID: <20110414053102.D2EBC151F83@gemini.denx.de> (raw)
In-Reply-To: <BANLkTinApAmm6hrcSofdYA6r7KUPMr8L+w@mail.gmail.com>

Dear Jason Liu,

In message <BANLkTinApAmm6hrcSofdYA6r7KUPMr8L+w@mail.gmail.com> you wrote:
> 
> Yes, I have already thought about it before I submit patches. The fact is that
> there is there are two DDR chips connected to CS0 and CS1 of MX53 on loco
> board, but each DDR chip is 512MB, but CS0 and CS1 can support up to 1GB,
> which means the memory space is not continuous, when set:

The mapping is fix, and you cannot remap it as a single, contiguous
region?

> gd->ram_size = get_ram_size((volatile void *)CONFIG_SYS_SDRAM_BASE,
>                           PHYS_SDRAM_1_SIZE + PHYS_SDRAM_2_SIZE);
> it will return the same as:
>
> gd->ram_size = get_ram_size((volatile void *)CONFIG_SYS_SDRAM_BASE,
>                             PHYS_SDRAM_1_SIZE);

You have always to test each bank on it's own, i. e.

	size1 = get_ram_size(..., PHYS_SDRAM_1_SIZE);
	size2 = get_ram_size(..., PHYS_SDRAM_2_SIZE);

	gd->ram_size = get_ram_size = size1 + size2;

> I think the gd->ram_size is just used for uboot, but

Right, but it is supposed to show the full RAM size, and not only half
of it (otherwise it should be gd->half_ram_size or similar ;-)

> If you still think that I really need fix it, I will do it.

THis needs fixing.

> > This has been discussed before: this code should be factored out into
> > common code.
>
> Yes, I think I can send out another clean up patch for it to fix all
> the boards including
> mx31/35/51/53 later.

No. Wrong order.  Please don't add to the mess and clean up later.
Instead, clean up now, and base your patch on th already cleaned up
code.

> > Please remove the '1' from all #defines that just enable features,
> > i.  e. where no specific numeric value is needed.
>
> Yes, I can send out another clean up patch to fix all the i.mx board config>  file

Again: No.  Please clean up NOW.

This patch will not be accepted as is.

> BTW, this patch set has been send out 2 months ago and Stefano has
> send out pull request
> to Albert and Albert has pulled in already, do you agree I send out
> another patch to address
> your comments? Thanks for your consideration.

No, this patch has serious bugs (memory size calculation) and other
issues (needs cleanup) and is thus rejected.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Anyone attempting to generate random numbers by deterministic  means
is, of course, living in a state of sin."          - John Von Neumann

  reply	other threads:[~2011-04-14  5:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 10:15 [U-Boot] [PATCH 1/1] MX5:MX53: support for freescale MX53LOCO board Jason Liu
2011-02-21 12:46 ` Stefano Babic
2011-02-22  1:44   ` Liu Hui-R64343
2011-02-22  6:53     ` Wolfgang Denk
2011-02-22  7:59       ` Jason Liu
2011-02-22 11:48     ` Stefano Babic
2011-02-21 23:38 ` Fabio Estevam
2011-02-22  1:47   ` Liu Hui-R64343
2011-02-22  3:28     ` Fabio Estevam
2011-02-22  6:54     ` Wolfgang Denk
2011-02-22  8:01       ` Jason Liu
2011-04-13 20:37 ` Wolfgang Denk
2011-04-14  3:26   ` Jason Liu
2011-04-14  5:31     ` Wolfgang Denk [this message]
2011-04-14  7:48       ` Jason Liu
2011-04-14  8:12         ` Jason Liu
2011-04-15 16:24           ` Stefano Babic
2011-04-15 17:32             ` Jason Liu

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=20110414053102.D2EBC151F83@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.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