From: Helmut Raiger <helmut.raiger@hale.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: zynq: fix a bug in Zynq linker script
Date: Wed, 25 Jun 2014 11:07:23 +0200 [thread overview]
Message-ID: <53AA914B.5020803@hale.at> (raw)
In-Reply-To: <53A01A8D.80401@monstr.eu>
On 06/17/2014 12:38 PM, Michal Simek wrote:
> On 06/17/2014 10:45 AM, Masahiro Yamada wrote:
>> ....
>>
>> This bug should be fixed asap.
>>
>> Because this patch is assigned to you,
>> could you apply it and send a pull-request, please?
> Applied and pull request sent.
>
> Thanks,
> Michal
>
This very same commit breaks the SPL on TT-01. Note, the SPL is not
contributed yet (I'm about to).
Has anyone tested a current u-boot on one of the mx31 boards lately?
Simply pulling in the vectors section in the linker script does not
do the trick.
I'm a bit tight with my time currently, so I'd very much appreciate if
someone could test and possibly offer a suggestion on what to change
to get that working again, if necessary.
Helmut
--
Scanned by MailScanner.
prev parent reply other threads:[~2014-06-25 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 10:47 [U-Boot] [PATCH] arm: zynq: fix a bug in Zynq linker script Masahiro Yamada
2014-06-17 8:45 ` Masahiro Yamada
2014-06-17 10:38 ` Michal Simek
2014-06-25 9:07 ` Helmut Raiger [this message]
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=53AA914B.5020803@hale.at \
--to=helmut.raiger@hale.at \
--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