[PATCH 1/1] Added arm64 assembly for examples/api crt0

[Brunham, Kalen]

Hi Tom,

What are next steps on this change?

I'm committed to the idea of EFI apps opposed to examples/standalone.
EFI currently requires block devices which is not enabled when only using flash.

Should config BLK be updated to include DM_SPI_FLASH?
Should we explore how to remove BLK as a dependency for EFI_LOADER?

Thanks.

-----Original Message-----
From: Tom Rini <trini at konsulko.com>
Sent: Monday, May 27, 2024 12:07 PM
To: Jiaxun Yang <jiaxun.yang at flygoat.com>
Cc: Brunham, Kalen <kalen.brunham at intel.com>; Heinrich Schuchardt <xypron.glpk at gmx.de>; Ilias Apalodimas <ilias.apalodimas at linaro.org>; U-Boot at lists.denx.de
Subject: Re: [PATCH 1/1] Added arm64 assembly for examples/api crt0

On Sat, May 25, 2024 at 05:20:43PM +0100, Jiaxun Yang wrote:
> 
> 
> 在2024年5月21日五月 下午7:15，Tom Rini写道：
> [...]
> >
> > We have long not done a great job with the U-Boot standalone API 
> > stuff, and for a number of years at this point a lot of the use 
> > cases it was used for could instead be filled by making an EFI 
> > application. There's a well defined API there, there's lots of 
> > examples, and frankly for the license related questions, makes a much nicer answer.
> 
> Hi Tom + U-Boot EFI folks,
> 
> Sorry for chime in here.
> 
> AFAIK there are quite a lot of users of U-Boot API in MIPS world, 
> mostly for Bare mental applications to perform chip diagnostic or programming stuff.

To be clear, I'm not saying we need to get rid of the ability to run random bare metal apps. Just the bit where U-Boot exposes some API for a few functions. We do not test it, and I do not know how well it works.
For what we provide there I would think just doing whatever one normally does for basic stdio functionality on bare metal would be fine instead.

But I do need to be louder about my intentions here before just doing it, so that others which do need / use it can chime in.

--
Tom