From: Mike Dunn <mikedunn@newsguy.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5] palmtreo680: add utility that writes u-boot to flash
Date: Sat, 20 Apr 2013 12:07:33 -0700 [thread overview]
Message-ID: <5172E775.70903@newsguy.com> (raw)
In-Reply-To: <201304202001.02570.marex@denx.de>
On 04/20/2013 11:01 AM, Marek Vasut wrote:
> Dear Mike Dunn,
>
>> On 04/20/2013 03:25 AM, Marek Vasut wrote:
>>> Dear Mike Dunn,
>>>
>>>
>>> I fixed the calloc() semantics and applied, thanks. Please repost
>>> whatever is still missing in u-boot-pxa/master and I'll then roll pullRQ
>>> for mainline.
>>
>> Oops, the board support patch is not in your tree either. Will repost.
>
> Did I not ramble about it? Check that first please, I'm not sure now ;-)
>
Yes, we went back-and-forth about it, and the latest version was v4. But I need
to rework it because the spl build now fails due to a recent change to
arch/arm/cpu/pxa/start.S in commit 7086e91b0e9930139e703c8f9f857b52baf2bef4
arm: relocate_code(): Use __image_copy_end for end of relocation
I was using my own linker script for the spl, which does not define the
__image_copy_end symbol that is now referenced in start.S. I don't exactly
remember why I felt the need to avoid using the script in
arch/arm/cpu/u-boot-spl.lds, except that I didn't like all the sections created
by the --ffunction-sections and --fdata-sections compiler flags and wanted them
combined with a '*' wildcard. But I removed my linker script and the
CONFIG_SPL_LDSCRIPT line from my config file and it is testing fine. So I will
have to post a v5 of the patch.
Thanks again Marek,
Mike
next prev parent reply other threads:[~2013-04-20 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 19:28 [U-Boot] [PATCH v5] palmtreo680: add utility that writes u-boot to flash Mike Dunn
2013-04-20 10:25 ` Marek Vasut
2013-04-20 16:37 ` Mike Dunn
2013-04-20 17:12 ` Marek Vasut
2013-04-20 17:53 ` Mike Dunn
2013-04-20 18:01 ` Marek Vasut
2013-04-20 19:07 ` Mike Dunn [this message]
2013-04-26 8:34 ` Smithlife
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=5172E775.70903@newsguy.com \
--to=mikedunn@newsguy.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