forked from Minki/linux
0c7596621e
Since we can't expect every user to read the EFI boot stub code it seems prudent to have a couple of paragraphs explaining what it is and how it works. The "initrd=" option in particular is tricky because it only understands absolute EFI-style paths (backslashes as directory separators), and until now this hasn't been documented anywhere. This has tripped up a couple of users. Cc: Matthew Garrett <mjg@redhat.com> Cc: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Matt Fleming <matt.fleming@intel.com> Link: http://lkml.kernel.org/r/1331907517-3985-4-git-send-email-matt@console-pimps.org Signed-off-by: H. Peter Anvin <hpa@zytor.com> |
||
|---|---|---|
| .. | ||
| i386 | ||
| x86_64 | ||
| 00-INDEX | ||
| boot.txt | ||
| earlyprintk.txt | ||
| efi-stub.txt | ||
| entry_64.txt | ||
| exception-tables.txt | ||
| mtrr.txt | ||
| pat.txt | ||
| usb-legacy-support.txt | ||
| zero-page.txt | ||