summaryrefslogtreecommitdiff
path: root/README.fallback
diff options
context:
space:
mode:
authorPeter Jones <pjones@redhat.com>2016-04-12 13:41:45 -0400
committerPeter Jones <pjones@redhat.com>2016-09-06 14:39:15 -0400
commit47f3a65eda2f864ea3a60aeb127cfec7bff64389 (patch)
treee66ec38dd0e9ffac556213cc7c41cd086da98cdf /README.fallback
parent6cbcfb727e1d42127e782e57f8b79268b9b2cff8 (diff)
downloadefi-boot-shim-47f3a65eda2f864ea3a60aeb127cfec7bff64389.tar.gz
efi-boot-shim-47f3a65eda2f864ea3a60aeb127cfec7bff64389.zip
Improve BOOT${ARCH}.CSV support.
Signed-off-by: Peter Jones <pjones@redhat.com>
Diffstat (limited to 'README.fallback')
-rw-r--r--README.fallback5
1 files changed, 3 insertions, 2 deletions
diff --git a/README.fallback b/README.fallback
index af2a354a..3f91c1ac 100644
--- a/README.fallback
+++ b/README.fallback
@@ -41,8 +41,9 @@ media. In that case, it'll invoke \EFI\BOOT\BOOTX64.EFI (or whatever
filename is right for your architecture.) In that case it'll be in
\EFI\BOOT, so it'll check for fallback.efi , and it'll find it and run
it. When it runs, fallback will look for every directory in \EFI\ with
-a BOOT.CSV in it, and it'll parse that, and create new boot variables
-from what it finds. Then it'll try to boot one of them.
+a BOOT${ARCH}.CSV in it, or BOOT.CSV if that's not found. It'll parse that,
+and create new boot variables from what it finds. Then it'll try to boot one
+of them.
BOOT.CSV is a UCS-2 LE formatted CSV file. So it has the LE byte order
marker, and after that it's just a series of lines, each having