From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/4] linux: config.in: add comment for Arm Cortex-M
Date: Fri, 1 Jun 2018 17:39:42 +0200 [thread overview]
Message-ID: <20180601153942.GA3841@scaer> (raw)
In-Reply-To: <1527772887-31616-4-git-send-email-christophe.priouzeau@st.com>
Christophe, All,
On 2018-05-31 13:21 +0000, Christophe PRIOUZEAU spake thusly:
> When binutils > 2.28 are selected on Arm Cortex-M cpu,
> linux kernel does not boot due to a new implementation
> of 'adr pseudo instruction' on binutils.
>
> Bugzilla thread: https://bugs.busybox.net/show_bug.cgi?id=11051
>
> Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com>
> ---
> Changes v1 -> v2
> - correct depends on for comment
>
> Changes v2 -> v3
> - use correct TAG BR2_ARM_CPU_ARMV7M
> - invert depends for BR2_ARM_CPU_ARMV7M
>
> linux/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/linux/Config.in b/linux/Config.in
> index 73a3299..b5957b6 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -8,6 +8,10 @@ config BR2_LINUX_KERNEL
>
> if BR2_LINUX_KERNEL
>
> +comment "Linux kernel will not boot with binutils >= 2.29"
> + depends on BR2_ARM_CPU_ARMV7M
So, my understanding was that the build in Thuimb mode was what was
causing the issue, rather than the actual architecture.
So, if one has (say) a Cortex-A9, and decides to build in Thumb mode, as
well as build its kernel in Thumb mode, wouldn't that also trigger the
issue as well?
Regards,
Yann E. MORIN.
> + depends on !BR2_BINUTILS_VERSION_2_28_X
> +
> # Packages that need to have a kernel with support for loadable modules,
> # but do not use the kernel-modules infrastructure, should select that
> # option.
> --
> 2.7.4
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-06-01 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 13:21 [Buildroot] [PATCH v3 1/4] Revert "configs/stm32f429: force usage of binutils 2.28.x" Christophe PRIOUZEAU
2018-05-31 13:21 ` [Buildroot] [PATCH v3 3/4] package/binutils: Cortex-M targets require version <2.29 Christophe PRIOUZEAU
2018-06-01 14:36 ` Peter Korsgaard
2018-06-01 15:42 ` Yann E. MORIN
2018-06-01 17:17 ` Peter Korsgaard
2018-05-31 13:21 ` [Buildroot] [PATCH v3 2/4] Revert "configs/stm32f469: force usage of binutils 2.28.x" Christophe PRIOUZEAU
2018-06-01 14:42 ` Peter Korsgaard
2018-05-31 13:21 ` [Buildroot] [PATCH v3 4/4] linux: config.in: add comment for Arm Cortex-M Christophe PRIOUZEAU
2018-06-01 14:39 ` Peter Korsgaard
2018-06-01 15:39 ` Yann E. MORIN [this message]
2018-06-01 17:21 ` Yann E. MORIN
2018-06-01 14:41 ` [Buildroot] [PATCH v3 1/4] Revert "configs/stm32f429: force usage of binutils 2.28.x" Peter Korsgaard
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=20180601153942.GA3841@scaer \
--to=yann.morin.1998@free.fr \
--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