From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support
Date: Thu, 04 Nov 2010 14:18:42 +0100 [thread overview]
Message-ID: <4CD2B2B2.9060902@ahsoftware.de> (raw)
In-Reply-To: <4CD2AD5C.3000809@free.fr>
Am 04.11.2010 13:55, schrieb Albert ARIBAUD:
> Then please do test this V3 patch and verify if the issues you raise
> still apply or are fixed.
V3 failed using my relocation-test-patch (and resulted in the same
problems as without any relocation patch). Therefor I've posted the
output. I though it was clear that I've used v3 (because of the subject).
> Please make sure to indicate which source commit you're testing on and
> which toolchain you're using, and to compare with V3 results.
I've created a tarball with the patches for the DockStar I'm currently
using for those tests.
It is available here:
http://ahsoftware.de/dockstar_uboot_patches.tar.bz2
Regards,
Alexander
next prev parent reply other threads:[~2010-11-04 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 18:24 [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 2/3] tx25: " Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 3/3] tx25: increase u-boot NAND size to match current build sizes Albert Aribaud
2010-11-03 18:27 ` [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert ARIBAUD
2010-11-04 10:26 ` Alexander Holler
2010-11-04 10:46 ` Alexander Holler
2010-11-04 12:40 ` Albert ARIBAUD
2010-11-04 12:47 ` Alexander Holler
2010-11-04 12:55 ` Albert ARIBAUD
2010-11-04 13:18 ` Alexander Holler [this message]
2010-11-04 16:56 ` Albert ARIBAUD
2010-11-04 18:37 ` Alexander Holler
2010-11-04 18:42 ` Alexander Holler
2010-11-04 19:20 ` Albert ARIBAUD
2010-11-04 19:39 ` Alexander Holler
2010-11-04 22:06 ` 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=4CD2B2B2.9060902@ahsoftware.de \
--to=holler@ahsoftware.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