> -----Original Message----- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Monday, May 16, 2016 1:09 PM > To: Amit Tomer <amittome...@gmail.com> > Cc: Bhupesh Sharma <bhupesh.sha...@nxp.com>; york sun > <york....@nxp.com>; u-boot@lists.denx.de; Peter Newton > <peter.new...@nxp.com> > Subject: Re: [U-Boot] [PATCH 5/5] ls2080ardb: Convert to distro boot > > > > > Am 16.05.2016 um 08:58 schrieb Amit Tomer <amittome...@gmail.com>: > > > >> On Sun, May 15, 2016 at 2:51 AM, Bhupesh Sharma > <bhupesh.sha...@nxp.com> wrote: > >> Note that UEFI firmware support is already available on LS2080A-RDB > >> and allows Booting distributions like CentOS on the same. > > > > Sorry to intervene here but it's about having the EFI support inside > > u-boot itself that may *not* required to have separate UEFI firmware > > to boot various distributions. > > > > Please correct, if it's not right ? > > It's correct. The idea is to allow everyone to boot using the uEFI > entry point in Linux (or any other OS), regardless of whether they want > to run U-Boot or a TianoCore based formware. > > This might seem useless today for embedded use cases, but some features > are only available via an EFI entry, such as kASLR. You can also invoke > Linux directly using the "bootefi" command, as Linux is an EFI binary > itself. That way the boot path doesn't become much longer than with > booti today. >
The default firmware being offered by NXP to boot distros on LS2080A and variants is UEFI. EFI application support in u-boot doesn't present a solution to things like run-time variable/service support that is required by distros to update firmware components on the go. And there are several other services being offered by UEFI to help distro boot e.g. secure uefi boot through x.509 certifications compliant to UEFI specifications. Regards, Bhupesh _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
