From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] MX31: mx31pdk: fix nand_spl
Date: Sun, 03 Apr 2011 19:50:12 +0200 [thread overview]
Message-ID: <4D98B354.8000606@denx.de> (raw)
In-Reply-To: <4D986353.5090505@free.fr>
On 04/03/2011 02:08 PM, Albert ARIBAUD wrote:
> Hi Stefano,
>
Hi Albert,
> Le 03/04/2011 12:01, Stefano Babic a ?crit :
>> Commit f326cbba98bae21d41df8daac0bd78121d557af1 breaks mx31pdk,
>> as the _end section in u-boot.lds is missing for the nand_spl
>> production.
>
> What command line should one use to reproduce the issue?
you should issue mx31pdk_nand. I do not know why there is a special
target in the Makefile, I do not think this is necessary and only
boards.cfg could be used. But this has nothing to do with the reported
error, answering your question I have seen something else strange ;-)
> I just did a
> ./MAKEALL mx31pdk from the current u-boot-arm master branch and it
> builds fine, which I suspect sould not be possible if it missed the _end
> symbol.
The mx31pdk supports booting from NOR or from NAND, using two different
configuration. You compiled for NOR, and everything works fine - only
the nand_spl part has this issue.
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-04-03 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 10:01 [U-Boot] [PATCH 1/2] MX31: mx31pdk: fix nand_spl Stefano Babic
2011-04-03 12:08 ` Albert ARIBAUD
2011-04-03 17:50 ` Stefano Babic [this message]
2011-04-03 22:27 ` Fabio Estevam
2011-04-03 22:04 ` Fabio Estevam
2011-04-04 5:52 ` Albert ARIBAUD
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=4D98B354.8000606@denx.de \
--to=sbabic@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