All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bump ATF version in arm_juno_defconfig ?
Date: Mon, 23 Apr 2018 22:17:13 +0200	[thread overview]
Message-ID: <20180423221713.275f1f66@windsurf> (raw)

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
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

             reply	other threads:[~2018-04-23 20:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 20:17 Thomas Petazzoni [this message]
2018-05-28 16:52 ` [Buildroot] Bump ATF version in arm_juno_defconfig ? Joao Pinto
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=20180423221713.275f1f66@windsurf \
    --to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.