u-boot.git/lib, branch v2017.11-rc1

efi_loader: Some console improvements for vidconsole

2017-09-20T09:29:35+00:00

1) use fputs() to reduce cache flushes from once-per-char to
   once-per-string
2) handle \r, \t, and \b in addition to just \n for tracking
   cursor position
3) cursor row/col are zero based, not one based

Signed-off-by: Rob Clark 
[agraf: s/unsigned/unsigned int/]
Signed-off-by: Alexander Graf

efi_loader: Correctly figure out size for vidconsole

2017-09-20T09:28:39+00:00

If stdout is vidconsole, we cannot rely on ANSI escape sequences to
query the size, as vidconsole cannot reply on stdin.  Instead special-
case this if stdout is vidconsole.

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: split out escape sequence based size query

2017-09-20T09:14:12+00:00

We need to do something different for vidconsole, since it cannot
respond to the query on stdin.  Prep work for next patch.

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: print GUIDs

2017-09-20T09:10:42+00:00

Utilize printf GUID support to print GUIDs.

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: set loaded image code/data type properly

2017-09-20T09:10:24+00:00

These should be set according to the image type.  Shell.efi and SCT.efi
use these fields to determine what sort of image they are loading.

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: add bootmgr

2017-09-20T09:08:01+00:00

Similar to a "real" UEFI implementation, the bootmgr looks at the
BootOrder and BootXXXX variables to try to find an EFI payload to load
and boot.  This is added as a sub-command of bootefi.

The idea is that the distro bootcmd would first try loading a payload
via the bootmgr, and then if that fails (ie. first boot or corrupted
EFI variables) it would fallback to loading bootaa64.efi.  (Which
would then load fallback.efi which would look for \EFI\*\boot.csv and
populate BootOrder and BootXXXX based on what it found.)

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: efi variable support

2017-09-20T09:00:57+00:00

Add EFI variable support, mapping to u-boot environment variables.
Variables are pretty important for setting up boot order, among other
things.  If the board supports saveenv, then it will be called in
ExitBootServices() to persist variables set by the efi payload.  (For
example, fallback.efi configuring BootOrder and BootXXXX load-option
variables.)

Variables are *not* currently exposed at runtime, post ExitBootServices.
On boards without a dedicated device for storage, which the loaded OS
is not trying to also use, this is rather tricky.  One idea, at least
for boards that can persist RAM across reboot, is to keep a "journal"
of modified variables in RAM, and then turn halt into a reboot into
u-boot, plus store variables, plus halt.  Whatever the solution, it
likely involves some per-board support.

Mapping between EFI variables and u-boot variables:

  efi_$guid_$varname = {attributes}(type)value

For example:

  efi_8be4df61-93ca-11d2-aa0d-00e098032b8c_OsIndicationsSupported=
     "{ro,boot,run}(blob)0000000000000000"
  efi_8be4df61-93ca-11d2-aa0d-00e098032b8c_BootOrder=
     "(blob)00010000"

The attributes are a comma separated list of these possible
attributes:

  + ro   - read-only
  + boot - boot-services access
  + run  - runtime access

NOTE: with current implementation, no variables are available after
ExitBootServices, and all are persisted (if possible).

If not specified, the attributes default to "{boot}".

The required type is one of:

  + utf8 - raw utf8 string
  + blob - arbitrary length hex string

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: make pool allocations cacheline aligned

2017-09-20T08:48:09+00:00

This avoids printf() spam about file reads (such as loading an image)
into unaligned buffers (and the associated memcpy()).  And generally
seems like a good idea.

Signed-off-by: Rob Clark 
[agraf: use __aligned]
Signed-off-by: Alexander Graf

efi_loader: support load_image() from a file-path

2017-09-20T08:45:28+00:00

Previously we only supported the case when the EFI application loaded
the image into memory for us.  But fallback.efi does not do this.

Signed-off-by: Rob Clark 
Signed-off-by: Alexander Graf

efi_loader: add file/filesys support

2017-09-20T08:43:54+00:00

fallback.efi (and probably other things) use UEFI's simple-file-system
protocol and file support to search for OS's to boot.

Signed-off-by: Rob Clark 
[agraf: whitespace fixes, unsigned fixes]
Signed-off-by: Alexander Graf