From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bump ATF version in arm_juno_defconfig ?
Date: Mon, 28 May 2018 17:52:07 +0100 [thread overview]
Message-ID: <b3321ee8-8265-e448-21fe-1b722cbb68ef@synopsys.com> (raw)
In-Reply-To: <20180423221713.275f1f66@windsurf>
Hi Thomas,
Hope you are doing fine!
?s 9:17 PM de 4/23/2018, Thomas Petazzoni escreveu:
> Hello Joao,
>
> You originally contributed the arm_juno_defconfig in Buildroot. It
> currently uses v1.2 of ATF, and I encountered a build failure with this
> ATF version as part of the Buildroot test suite:
>
> ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
> context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
> context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'
>
> This issue has been fixed since ATF v1.3. Do you think you could
> provide a patch bumping the ATF version ? The latest version is ATF
> v1.5, so if you could bump the defconfig, it would be nice.
>
> In addition, it would be great if you could send a patch adding
> yourself in the DEVELOPERS file for this platform, so we easily know who
> to contact for questions related to this platform.
>
> Thanks!
>
> Thomas
>
My team member Gustavo will check this out and he will be the maintainer if it
is ok for you.
Thanks,
Joao
next prev parent reply other threads:[~2018-05-28 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 20:17 [Buildroot] Bump ATF version in arm_juno_defconfig ? Thomas Petazzoni
2018-05-28 16:52 ` Joao Pinto [this message]
2018-05-28 19:27 ` Thomas Petazzoni
2018-08-12 15:03 ` Thomas Petazzoni
2018-08-17 12:15 ` Joao Pinto
2018-08-21 16:42 ` Gustavo Pimentel
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=b3321ee8-8265-e448-21fe-1b722cbb68ef@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=buildroot@busybox.net \
/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