On Tue, Jun 02, 2015 at 11:59:09AM +0100, Ryan Harkin wrote:
> I think the best way is to define Shell.efi as the default boot entry and
> then to provide startup.nsh on a boot device.

I would very strongly advise against this.

> startup.nsh then contains a command to boot the kernel, eg:
>
>     Image dtb=file.dtb initrd=ramdisk.img <kernel commandline>
>
> But if you want a default BDS option to boot the kernel directly, you can
> also do this with type 0 device, set PcdDefaultBootDevicePath to be the
> path to your kernel image, then set PcdDefaultBootArgument to something
> like:
>
>     dtb=file.dtb initrd=ramdisk.img <kernel commandline>

Specifying dtb= on the command line is not supported when enabling
Secure Boot. Which may not be a problem now, but will be in the future
if we build our infrastructure around this.

> i.e the same as before, only leave out the filename of the Image file.
>
> I wouldn't use all that other stuff.

"That other stuff" is also known as the UEFI boot mechanism.

If we are
not using it, we should not be calling it UEFI.

/
    Leif