Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x
Date: Wed, 30 May 2018 17:42:57 +0200	[thread overview]
Message-ID: <20180530174257.616403f2@windsurf.home> (raw)
In-Reply-To: <98410cef-37c3-0450-9142-e1df5df34eaa@st.com>

Hello,

On Wed, 30 May 2018 15:24:19 +0000, Christophe PRIOUZEAU wrote:

>   I know that my patches are not a durable solution.
>   My concern are to have a solution for stm32  and not keep
> this state on which stm32 board doesn't boot.

Hence my proposal to generalize your change so that it covers all
Cortex-M platforms and not just the STM32 defconfigs.

Your solution is not even generic enough for STM32: it only makes the
STM32 defconfigs work. But if:

 - Someone uses the defconfig and changes the binutils version to 2.29,
   it won't work anymore.

 - Someone creates his own defconfig for another custom STM32 platform
   and uses binutils 2.29, it won't work.

So I repeat that the change of the defconfigs is the bad solution. If
binutils 2.29 really doesn't work for Cortex-M platforms, the fix is to
change the binutils package to exclude 2.29+ from being selected on
Cortex-M platforms.

>   For the long term solution, I have seen a patch on the kernel
> to correct the issue around 'adr pseudo instruction'.
> Patch: https://patchwork.kernel.org/patch/10072631/
> "arm: ensure symbol is a thumb symbol in new binutils".
> This patch are not merged on the kernel, I have tested it on top
> of kernel 4.11(buildroot config) and kernel 4.17-rc5, the patch
> work correctly, we are able to perform a  complete boot.
> I need to continue my test to see if this patch is sufficient.

Thanks for working on this upstream with the kernel people.

However, we'll of course still have the "gap" that any kernel before
the one having your fix will be broken with binutils 2.29+. I don't
think there anything we can do about this though.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-05-30 15:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 12:09 [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x Christophe PRIOUZEAU
2018-05-29 12:09 ` [Buildroot] [PATCH 2/2] configs/stm32f469: " Christophe PRIOUZEAU
2018-05-29 12:49   ` Romain Naour
2018-05-29 12:39 ` [Buildroot] [PATCH 1/2] configs/stm32f429: " Romain Naour
2018-05-29 12:47   ` Christophe PRIOUZEAU
2018-05-29 12:48   ` Romain Naour
2018-05-29 15:51 ` Peter Korsgaard
2018-05-29 21:32 ` Thomas Petazzoni
2018-05-30 12:12   ` Laurent GONZALEZ
2018-05-30 16:24     ` Yann E. MORIN
2018-05-30 15:24   ` Christophe PRIOUZEAU
2018-05-30 15:42     ` Thomas Petazzoni [this message]
2018-05-30 20:35       ` Arnout Vandecappelle
2018-05-30 20:41         ` Thomas Petazzoni
2018-05-30 20:46           ` Romain Naour
2018-05-31  8:34           ` Christophe PRIOUZEAU
2018-05-31  9:13             ` Arnout Vandecappelle
2018-05-31  9:16             ` Thomas Petazzoni

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=20180530174257.616403f2@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox