From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] add nand spl boot for qi_lb60 board
Date: Fri, 6 Jan 2012 13:05:31 -0600 [thread overview]
Message-ID: <4F0745FB.1050205@freescale.com> (raw)
In-Reply-To: <4F06CA68.8020800@openmobilefree.net>
On 01/06/2012 04:18 AM, Xiangfu Liu wrote:
> On 01/06/2012 02:44 AM, Scott Wood wrote:
>> Use "mips-whatever-objdump -dlrsh" on the good and bad u-boot binaries
>> (or on any .o files you suspect may be relevant), to see more
>> specifically what's different.
>>
>> You may also want to try compiling suspect files to assembly and
>> comparing the differences there.
>>
>> -Scott
>
> thanks Scott. a working patch is coming soon.
>
> forget add CONFIG_SYS_NAND_4BIT_HW_ECC_OOBFIRST to board configure head
> file.
That still doesn't explain how a few duplicate externs changed the
resulting binary...
-Scott
next prev parent reply other threads:[~2012-01-06 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 11:31 [U-Boot] add nand spl boot for qi_lb60 board Xiangfu Liu
2012-01-04 22:01 ` Scott Wood
2012-01-04 22:12 ` Scott Wood
2012-01-05 0:24 ` Xiangfu Liu
2012-01-05 18:44 ` Scott Wood
2012-01-06 10:18 ` Xiangfu Liu
2012-01-06 19:05 ` Scott Wood [this message]
2012-01-10 9:14 ` Xiangfu 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=4F0745FB.1050205@freescale.com \
--to=scottwood@freescale.com \
--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