Hi Tom, Fundamentally I want to create standalone applications that can be used to help debug low-level HW issues. The advantage to doing this in U-Boot is to leverage existing drivers and other facilities. I agree this is niche, but is something I saw one of our power-users do recently and are looking to share with our customers. Unfortunately, the Makefiles today make this more difficult than it should be, hence the desire to change this. My current goal is to enable a user to use the stock (unpatched) u-boot to minimally create a hello-world that they can execute following the existing examples/standalone steps.
Are your plans to deprecate both API and Standalone? -----Original Message----- From: Tom Rini <tr...@konsulko.com> Sent: Tuesday, May 21, 2024 12:47 PM To: Brunham, Kalen <kalen.brun...@intel.com> Cc: U-Boot@lists.denx.de Subject: Re: [PATCH 1/1] Added arm64 assembly for examples/api crt0 On Tue, May 21, 2024 at 04:44:54PM +0000, Brunham, Kalen wrote: > I don't specifically need API, but today this is needed to enable > creation of standalone applications which does work on our ARM64. > > If the concern is fixing this startup code, then I can come back with > a change to the KConfig and Makefiles to enable compiling the > hello_world standalone example for ARM64. But still, why are you doing that? Removing the standalone API itself is on my TODO list, so understanding why someone would be using that today rather than just making an EFI application would be helpful. -- Tom
