在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.
But I'd agree that there is no benefit to maintain ABI stuff in upstream for long run.
However, I think people still need an API-like interface for those simple applications, while many architectures are not supported by U-Boot EFI for now.
Sadly, most architectures are not covered by UEFI spec, some of them are violating fundamental assumptions of UEFI spec, like no 1:1 PA VA mapping or simply being Big Endian.
Do you think it's a good idea to port EFI support to as many architectures as possible, and produce U-Boot supplements to UEFI spec to cover those details? I'm happy to look into it.
Thanks
That there's some power users out there making use of standalone to do useful things is news to me. Some of them speaking up and offering to be visible in maintaining it would be good (there's Coverity issues and lack of CI testing, which should be addressed).
-- Tom
附件:
- signature.asc