From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Sun, 27 Dec 2015 16:33:36 +0100 Subject: [U-Boot] [PATCH 8/9] efi_loader: Add "bootefi" command In-Reply-To: <20151226185512.GB25034@bivouac.eciton.net> References: <1450792676-109541-1-git-send-email-agraf@suse.de> <1450792676-109541-9-git-send-email-agraf@suse.de> <567D0634.4010302@suse.de> <567D0B82.2030108@suse.de> <20151226185512.GB25034@bivouac.eciton.net> Message-ID: <568004D0.1010309@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 26.12.15 19:55, Leif Lindholm wrote: > On Fri, Dec 25, 2015 at 10:25:22AM +0100, Andreas F?rber wrote: >> Am 25.12.2015 um 10:02 schrieb Alexander Graf: >> [snip] >>> The reason I implemented "bootefi" was really because it's the natural >>> fit into how U-Boot handles all other formats today. I don't think this >>> is going to be the last patch set around EFI support. >> >> I think what Matwey was suggesting is integrating your "bootefi" into >> the standard "distro" boot sequence environment, so that it probes each >> device for an EFI binary and if it finds one runs load and bootefi, >> without the need for any boot.scr. >> >> That would be a follow-up patch. >> >> It however conflicts with your idea of having some potentially >> board-specific code mess with "fdt addr" command before running "bootefi". > > This could however be resolved by moving to a model where the > device-tree was considered a component of the firmware (which is how > we treat it in UEFI). If U-Boot had an awareness (if it does not > already) of an FDT being something it should have and know about, then > this could trivially be passed onto bootefi. > This could means a "default_fdt" environment variable which is loaded > automatically before bootcmd is executed. That part is already the case in my patches :). The difficult bit is what to do when it doesn't work, because the kernel guys consider a dtb to be a "Linux configuration" framework rather than the "hardware description" framework it's supposed to be. Alex