From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Thu, 31 Aug 2017 15:58:36 +0200 Subject: [U-Boot] [PATCH 01/23] efi_loader: allow return value in EFI_CALL In-Reply-To: References: <20170826225110.7381-1-xypron.glpk@gmx.de> <20170826225110.7381-2-xypron.glpk@gmx.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 08/31/2017 02:51 PM, Simon Glass wrote: > On 27 August 2017 at 06:51, Heinrich Schuchardt wrote: >> Macro EFI_CALL was introduced to call an UEFI function. > Should this be 'an EFI'. Or 'a UEFI'? In a nutshell, EFI is the v1, proprietary, for pay, closed protocol while UEFI is v2 and what edk2 implements, what you can get specs for, etc. But since people started implementing things for v1 back in the day and they are reasonable compatible, nobody calls UEFI UEFI, but just EFI :). It's a mess and I certainly didn't help it by calling everything EFI, but it's what we're in and we should rather stay coherent IMHO. So EFI_CALL really does call UEFI functions ;). Alex