Comment 12 for bug 1131141

If we don't have persistence of the UEFI config then we are going to have to create a new device class in the dispatcher. This may not be a bad thing, but it means it's not a 30 minute fix either.

Essentially, we treat UEFI like a sort of uBoot monitor. With uBoot we look for the appropriate uBoot prompt after issuing commands. With UEFI we say the boot prompt is "Start: " - when we see that we issue the UEFI boot config number (2 for Ubuntu, 3 for Adnroid) and that's it. Without persistent storage we will have to issue the set of options and strings to configure a new boot. Only problem is that as it stands, LAVA will time out (just for fun I tried it to prove my point) waiting for "Start: " after we issue the "a" for Boot Manager.

What I will need to do is create a new device type that will allow us to look for the appropriate messages, and then set up the config. It's not rocket science, but it's going to take time to implement.

The question is, what are the chances of getting persistent UEFI config in the near term?