Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Jonathan Ben Avraham <yba@tkos.co.il>,
	Romain Naour <romain.naour@gmail.com>,
	Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/4] arch/Config.in.xtensa: adjust endianness logic to avoid bogus configurations
Date: Sun, 25 Sep 2022 10:30:19 +0200	[thread overview]
Message-ID: <20220925103019.1febbac3@windsurf> (raw)
In-Reply-To: <20220925072502.GU1419013@scaer>

Hello,

On Sun, 25 Sep 2022 09:25:02 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> >  (1) Showing the overlay file option only when building an internal
> >      toolchain. For external toolchain configurations, it does not
> >      make sense to show it as it will have no effect.  
> 
> This should be a separate patch.

ACK.

> >  (2) Showing the endianness choice either for internal toolchain
> >      configurations with non-empty BR2_XTENSA_OVERLAY_FILE, or for
> >      external toolchain configurations.  
> 
> As an empty BR2_XTENSA_OVERLAY_FILE is not accepted anymore (see below),

See my patch 2/4. Not accepting an empty BR2_XTENSA_OVERLAY_FILE is
totally wrong, as it breaks the build with external toolchains.
External toolchains can target a custom Xtensa core, but specifying a
overlay file with an external toolchain does not make any sense.

My patch 2/4 therefore reverts 4cbf7336914f, which is wrong.

> this can be simplified to "sharing the endianness chice for internal and
> external toolchains".
> 
> >  (2) Defaulting to BE when BR2_XTENSA_OVERLAY_FILE is empty.  
> 
> An empty BR2_XTENSA_OVERLAY_FILE is now no longer accepted, after commit
> 4cbf7336914f (arch/xtensa: custom configuration requires an overlay).

Right, but this commit is incorrect, and needs to be reverted.

> > Fixes:
> >   http://autobuild.buildroot.net/results/702e2886156f291466375dfcf412c20f1aa5857d/  
> 
> This commit if from August the 15th; I could not find any such failure
> since 4cbf7336914f was applied; the last occured 2022-09-08, on commit
> d2141f65e449, which is the parent of 4cbf7336914f (there are build
> failures on older branches, of course, but not on master).

See above: 4cbf7336914f is incorrect. It breaks for example the test
case for the Bootlin Xtensa LX60 external toolchain. An empty overlay
file is perfectly valid for a custom Xtensa core, when using an
external toolchain.

And I am precisely doing the revert *after* this patch 1/4 so that the
series is bisectable. I.e introduce the correct fix, and then remove
the incorrect fix.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-25  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 20:53 [Buildroot] [PATCH 1/4] arch/Config.in.xtensa: adjust endianness logic to avoid bogus configurations Thomas Petazzoni via buildroot
2022-09-24 20:53 ` [Buildroot] [PATCH 2/4] Revert "arch/xtensa: custom configuration requires an overlay" Thomas Petazzoni
2022-09-24 20:53 ` [Buildroot] [PATCH 3/4] arch/{Config.in, arch.mk}.xtensa: add explicit support for DC233C core Thomas Petazzoni
2022-09-24 20:53 ` [Buildroot] [PATCH 4/4] configs/qemu_xtensa_lx60*: use new BR2_xtensa_dc233c option Thomas Petazzoni
2022-09-25  7:25 ` [Buildroot] [PATCH 1/4] arch/Config.in.xtensa: adjust endianness logic to avoid bogus configurations Yann E. MORIN
2022-09-25  8:30   ` Thomas Petazzoni [this message]
2022-09-25  8:38     ` 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=20220925103019.1febbac3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=yann.morin.1998@free.fr \
    --cc=yba@tkos.co.il \
    /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