From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
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 v2 1/5] arch/Config.in.xtensa: adjust endianness logic to avoid bogus configurations
Date: Mon, 31 Oct 2022 22:02:26 +0100 [thread overview]
Message-ID: <20221031220226.36f3ccf8@windsurf> (raw)
In-Reply-To: <20220925101041.GH1127102@scaer>
Hello,
Sorry to bring back this topic only now, but there are still Xtensa
issues that we need to resolve, and this series was aiming at solving
them. But I have further questions.
On Sun, 25 Sep 2022 12:10:41 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > diff --git a/arch/Config.in.xtensa b/arch/Config.in.xtensa
> > index f9d5adb4c9..4bb58e1964 100644
> > --- a/arch/Config.in.xtensa
> > +++ b/arch/Config.in.xtensa
> > @@ -37,6 +37,10 @@ config BR2_XTENSA_LITTLE_ENDIAN
> >
> > config BR2_XTENSA_BIG_ENDIAN
> > bool "Big endian"
> > + # Internal toolchains without an overlay file are always
> > + # little-endian, so we prevent from selecting big endian in
> > + # this case.
> > + depends on BR2_XTENSA_OVERLAY_FILE != "" || BR2_TOOLCHAIN_EXTERNAL
>
> I think that dependency should go to the whole choice instead:
>
> choice
> prompt "Target Architecture Endianness"
> default BR2_XTENSA_LITTLE_ENDIAN
> depends on BR2_XTENSA_CUSTOM || BR2_TOOLCHAIN_EXTERNAL
My memory is probably vague, but I don't see how this solve the
problem. The problem was to prevent the user from choosing "big endian"
if he has selected a custom core but not specified an overlay.
> This should cover the external toolchain case, and the internal
> toolchain for a custom core (assuming we keep the no-empty overlay for
> custom cores).
Not sure what you mean by "assuming we keep the no-empty overlay for
custom cores".
>
> I.e. semantically, choosing between big or little is not about having or
> not having an overlay, but about being a custom core or not (or using a
> custom toolchain).
Not sure to follow you here. The only issue is precisely that if you
don't specify an overlay, there is no way your custom Xtensa core can
be big endian: it will be little endian. The configuration we want to
prevent the user from creating is: custom core, no overlay, big endian.
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
next prev parent reply other threads:[~2022-10-31 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 9:09 [Buildroot] [PATCH v2 0/5] Fixes/improvements in Xtensa handling Thomas Petazzoni
2022-09-25 9:09 ` [Buildroot] [PATCH v2 1/5] arch/Config.in.xtensa: adjust endianness logic to avoid bogus configurations Thomas Petazzoni
2022-09-25 10:10 ` Yann E. MORIN
2022-10-31 21:02 ` Thomas Petazzoni via buildroot [this message]
2022-09-25 9:09 ` [Buildroot] [PATCH v2 2/5] Revert "arch/xtensa: custom configuration requires an overlay" Thomas Petazzoni
2022-09-25 10:03 ` Yann E. MORIN
2022-09-25 10:13 ` Thomas Petazzoni
2022-10-31 21:05 ` Thomas Petazzoni via buildroot
2022-09-25 9:09 ` [Buildroot] [PATCH v2 3/5] arch/Config.in.xtensa: use one line per case in BR2_ENDIAN definition Thomas Petazzoni
2022-09-25 9:09 ` [Buildroot] [PATCH v2 4/5] arch/{Config.in, arch.mk}.xtensa: add explicit support for DC233C core Thomas Petazzoni
2022-09-25 9:09 ` [Buildroot] [PATCH v2 5/5] configs/qemu_xtensa_lx60*: use new BR2_xtensa_dc233c option 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=20221031220226.36f3ccf8@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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