On Mon, Aug 5, 2013 at 7:12 AM, Dave Martin <Dave.Martin@xxxxxxx> wrote: > On Fri, Aug 02, 2013 at 02:29:02PM -0700, Roy Franz wrote: >> The ARM kernel also has an EFI stub which works largely the same way >> as the x86 stub, so move the documentation out of x86 directory and >> update to reflect that it is generic, and add ARM specific text. >> >> Signed-off-by: Roy Franz <roy.franz@xxxxxxxxxx> >> --- >> Documentation/efi-stub.txt | 78 ++++++++++++++++++++++++++++++++++++++++ >> Documentation/x86/efi-stub.txt | 65 --------------------------------- >> arch/x86/Kconfig | 2 +- >> 3 files changed, 79 insertions(+), 66 deletions(-) >> create mode 100644 Documentation/efi-stub.txt >> delete mode 100644 Documentation/x86/efi-stub.txt >> >> diff --git a/Documentation/efi-stub.txt b/Documentation/efi-stub.txt >> new file mode 100644 >> index 0000000..7837df1 >> --- /dev/null >> +++ b/Documentation/efi-stub.txt >> @@ -0,0 +1,78 @@ >> + The EFI Boot Stub >> + --------------------------- >> + >> +On the x86 and ARM platforms, a bzImage can masquerade as a PE/COFF image, >> +thereby convincing EFI firmware loaders to load it as an EFI >> +executable. The code that modifies the bzImage header, along with the > > > Minor nit, I don't think there is such a thing as "bzImage" for ARM. > > Cheers > ---Dave > Yeah, I don't thinks so either... How about: On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade.... Roy -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
