Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] linux: may fail to boot for binutils 2.29+ even without armv7m
Date: Tue, 5 Jun 2018 17:43:32 +0200	[thread overview]
Message-ID: <20180605154332.GC2503@scaer> (raw)
In-Reply-To: <b6e193cb-d79d-3758-859a-e8c80933947f@gezedo.com>

Laurent, All,

On 2018-06-05 09:23 +0200, Laurent GONZALEZ spake thusly:
> On 05/06/2018 07:49, Thomas Petazzoni wrote:
> > On Tue, 5 Jun 2018 00:10:30 +0200, Arnout Vandecappelle wrote:
> >>>  comment "Linux kernel may fail to boot with binutils >= 2.29"
> >>> -	depends on BR2_ARM_CPU_ARMV7M
> >>> +	depends on BR2_arm || BR2_armeb  
> >>  I have a bit of a problem with this patch. IMO it's rather unlikely that people
> >> build the kernel in THUMB mode on non-M CPUs.
> > Are you sure ? There is definitely support for building a Thumb2 kernel
> > on ARMv7-A, and I think it's a popular way to reduce a bit the size of
> > the kernel, no?
> I gently remember the list that we can alternatively fix the kernel with a patch.

Not really, because we don;t know where the kernel is coming from, and
if it is already patched or not, or if it has a similar construct
elsewhere in the code.

A lot of users, especially enterprise-class citizen, have their own
internal git tree(s) with their own kernel patched for their own
bioard(s), to which they may also apply various unknown sets of patches,
so they may already have that patch applied in those internal trees.

Granted, we could have a conditional patch, like the perl deprecated
stuff, but I don;t much like that idea, because it is not bullet-proof
(e.g. their tree already has a patch that touches close to where our
patch would be applied, so they conflict, so our patch does not apply,
so we believe their kernl is OK while it is not, and the runtime fails,
and we're back to square-one).

Granted, this is very unlikely, but the more unlikely things tend to be 
in theory, the more they tend to happen in the real world! ;-)

> This solution will allow any version of binutils to work with any version of the kernel, and can be easily reverted.
> 
> What about using:
> 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-March/565390.html

That patch has still not been applied in v4.17, so I'd be wary of using
a patch that is not a backport anyway... And BTW, v4.17 is still unfixed
as far as I can see...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-06-05 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 18:01 [Buildroot] [PATCHv2] linux: may fail to boot for binutils 2.29+ even without armv7m Yann E. MORIN
2018-06-01 19:42 ` Peter Korsgaard
2018-06-04 22:10 ` Arnout Vandecappelle
2018-06-05  5:49   ` Thomas Petazzoni
2018-06-05  7:23     ` Laurent GONZALEZ
2018-06-05 15:43       ` Yann E. MORIN [this message]
2018-06-05 15:29     ` Yann E. MORIN
2018-06-08 14:22       ` Peter Korsgaard
2018-06-08 17:15         ` Yann E. MORIN
2018-06-05 15:25   ` Yann E. MORIN
2018-06-08 14:19   ` Peter Korsgaard
2018-06-17 15:04 ` 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=20180605154332.GC2503@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