On Mon, Sep 30, 2013 at 10:28:49PM +0100, Grant Likely wrote:

...

...

load image protocol. In that case the sub should override the setting in

the

...

...

FDT if the initrd argument is present.

Hmm, well, it's slightly worse than that - it will have one; only it will be GRUB's command line.

The way that can be resolved is:

• FDT present?

- Commandline present in FDT chosen node?     - Yes       - Use that.     - No       - EFI_LOADED_IMAGE command line present?         - Yes           - Use that.         - No           - Fail miserably.

That doesn't handle the case where firmware provides the fdt, but the kernel is loaded via the UEFI shell or gummiboot. In that case the stub must process both the loaded image arguments.

Well, unless the firmware-provided device tree contains a kernel command line, that should work fine?

If you mean that there are two command lines to parse for the EFI_LOADED_IMAGE (one for shell/gummiboot), surely there is a handle in there to identify the "current" one.

/ Leif