From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] examples: make examples customizable
Date: Tue, 22 Sep 2020 16:18:09 -0400 [thread overview]
Message-ID: <20200922201809.GL14816@bill-the-cat> (raw)
In-Reply-To: <69c71a63-2029-c677-325e-9a07d8346d9d@gmx.de>
On Tue, Sep 22, 2020 at 08:49:20PM +0200, Heinrich Schuchardt wrote:
> On 9/22/20 8:42 PM, Tom Rini wrote:
> > On Tue, Sep 22, 2020 at 08:03:49PM +0200, Heinrich Schuchardt wrote:
> >
> >> Most users don't need the standalone API examples. Distributions like Suse
> >> do not supply libgcc for cross-compiling and we cannot do without on ARMv8
> >> for building examples/.
> >>
> >> Make examples customizable via symbol CONFIG_EXAMPLES. It only defaults to
> >> yes to ensure that we compile it on Gitlab CI.
> >
> > In this case we should not make it "default y" but instead enable it in
> > some specific cases that go through CI. Probably once per arch/
> > directory on the QEMU / virtual target for that arch.
>
> default y if ARCH_QEMU would compile it
OK, lets do that in v2 please.
> >> Cc: Matthias Brugger <mbrugger@suse.com>
> >> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >> ---
> >> I wonder if we should not completely drop the standalone API. The UEFI API
> >> has enough to run a standalone application.
> >
> > I'm certainly in favor of NOT adding support there for new
> > architectures. I don't believe however we can drop it for existing
> > architectures without some fairly large notice, and only then when UEFI
> > is available as a reasonable replacement (ARM? Yes. MIPS? No idea).
> >
>
> UEFI is low endian only.
Right, so we can't just remove the standalone API but we can encourage
new architectures to see if UEFI is right for them.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200922/63b8bd2a/attachment.sig>
next prev parent reply other threads:[~2020-09-22 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 18:03 [PATCH 1/1] examples: make examples customizable Heinrich Schuchardt
2020-09-22 18:03 ` Heinrich Schuchardt
2020-09-23 11:37 ` Matthias Brugger
2020-09-22 18:42 ` Tom Rini
2020-09-22 18:49 ` Heinrich Schuchardt
2020-09-22 20:18 ` Tom Rini [this message]
2020-09-22 18:47 ` Simon Glass
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=20200922201809.GL14816@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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